Merge conflict Gerrit cannot merge this change. It needs a rebase onto main.

Review main Ready for review

96852[TASK] Add check whether a user may read a field

Oli Bartsch CR 0 V 0 Hard +320 −3 updated 11/18/26, 20:42

Commit message

An API that hands out field values of records for a backend user needs
to know which fields it may hand out. The core decides this in
BackendUtility::getAllowedFieldsForTable(), which lives in the backend
extension, reads the global user and lists fields a reader must not
get, such as passthrough columns for admins.

The FieldVoter now decides on reading a field as well:
isGranted(Scope::READ, SchemaField::fromSchema($schema, $field)).
Exclude fields need a grant in non_exclude_fields, as for writing.
Password fields and fields that require a step-up authentication by
authenticationContext hold secrets and are never readable, not even for
admins.

The internal RecordFieldReadAccessCheck decides for the principal of the
request, a table and a field name, without a record. The table must be
readable, as decided by the TableVoter, and the field by the FieldVoter.
uid, pid and the tstamp and crdate fields are readable as well, and
admins also read the sortby, delete, versioning, description and
language fields. Columns of type passthrough, none, user, flex and json
are not handed out, not even to admins, as they hold internal data or
values only a renderer can interpret.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 2
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/52/96852/2 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/52/96852/2 && git cherry-pick FETCH_HEAD

Review

  • Code review CR 0 Needs a vote
  • Verified V 0 Needs a vote
    • core-ci +1 CI

Relation chain 5

  1. 96852 [TASK] Add check whether a user may read a field This change

  2. main 96580[TASK] Add check whether a user may read a record This change is based on it Merge conflict Oli Bartsch CR 0 V 0 Expert +1773 −28
  3. main 97323[TASK] Check page access along the cached page ancestry This change is based on it Merge conflict Benni Mack CR 0 V 0 Normal +166 −1
  4. main 97322[FEATURE] Decide page permissions with a security voter This change is based on it Benni Mack CR 0 V 0 Expert +1489 −151
  5. main 95784[FEATURE] Decide table, field and language access with voters This change is based on it Thomas Maroschik CR +1 V +1 unified-identity-security-kernel Expert +1215 −11

Issues 1

Files 7

Review log 35

  1. Oli Bartsch uploaded patch set 1 10/19/26, 07:27

  2. core-ci voted on patch set 1 V +1 10/19/26, 07:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/111591

  3. Simon Schaufelberger voted on patch set 1 CR +1 V +1 10/19/26, 19:37

  4. Benni Mack uploaded patch set 2 CR +1 V +1 11/18/26, 20:33

  5. core-ci voted on patch set 2 V +1 11/18/26, 20:42 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114923