#111293Extbase controller action argument mapping should respect persistence.storagePid restrictions
Description
When Extbase automatically resolves a domain object from a controller action argument, the configured persistence.storagePid restriction is ignored. For example:
public function showAction(Post $post): ResponseInterface
A record can be resolved by its UID even if it is stored outside the configured storage PIDs. While this behavior appears to be intentional and is documented, it may not be the best default.
Why this matters
Regular Extbase repository queries generally respect persistence.storagePid by default, with exceptions such as findByUid(). However, automatic controller argument mapping does not respect this restriction. This inconsistency is easy to overlook and may lead to unintended access to records outside the current plugin’s scope, particularly in multi-site setups or installations with separate data storage areas.
Suggested improvement
Automatic controller argument mapping should respect the configured persistence.storagePid restrictions by default, while providing an explicit way to opt out when necessary. Since changing the existing behavior could affect backward compatibility, a configurable solution or a change in a future major version might be appropriate.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Extbase controller action argument mapping should respect persistence.storagePid restrictions Resolves: #111293 Releases: main
Related issues 2
History 2
-
Garvin Hicking changed Related to #68157 <span data-processor="relativetime" data-value="2026-10-30T15:25:08+00:00" > 10/30/26, 15:25 </span>
-
Garvin Hicking changed Related to #95053 <span data-processor="relativetime" data-value="2026-10-30T15:25:16+00:00" > 10/30/26, 15:25 </span>