CVE-2026-63669: CWE-639: Authorization Bypass Through User-Controlled Key in apostrophecms apostrophe
ApostropheCMS versions prior to 4.32.0 contain an authorization bypass vulnerability in the page move operation. A regression in the move authorization guard disables the check that ensures a page can only be moved into a parent page the user has create rights over. This allows any authenticated user with edit rights on a page to move it under a restricted parent they lack create or edit permissions for. The move triggers an unchecked database update that re-ranks the restricted parent's children, potentially affecting documents the user cannot edit. The vulnerability is reachable via the documented REST API PATCH/PUT route with attacker-controlled parameters.
AI Analysis
Technical Summary
ApostropheCMS enforces per-type authorization on pages, including create and edit roles. The move() operation is intended to restrict moving pages only into parents where the user has create rights. However, a regression introduced in commit 9f72bd229be07e537a2ae894f4527f2fe6bcd3bd added a condition that gates the critical create permission check on the old parent being an archive page. For normal moves, this condition evaluates to false, effectively disabling the destination authorization check. Consequently, the only permission check is whether the user can edit the page being moved, which low-privileged editors can do for their own pages. This flaw allows moving pages under restricted parents without proper authorization. The move triggers an unguarded updateMany operation that re-ranks the restricted parent's children, modifying documents the user cannot edit. The vulnerability is exploitable via the documented REST API PATCH/PUT /api/v1/@apostrophecms/page/:_id route by controlling the _targetId and _position fields. The sibling insert route correctly enforces create permissions on the target, highlighting the regression in move().
Potential Impact
An authenticated user with edit rights on at least one page can bypass intended authorization controls to move that page under a restricted parent page they do not have create or edit permissions for. This unauthorized move triggers an unchecked database update that re-ranks the restricted parent's children, potentially modifying documents the user is not authorized to edit. The vulnerability does not disclose content or escalate privileges directly but allows unauthorized modification of page hierarchy and ordering, which may impact content integrity and access control enforcement.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict edit permissions to trusted users only and monitor for suspicious use of the page move API. Avoid exposing the PATCH/PUT /api/v1/@apostrophecms/page/:_id endpoint to untrusted users if possible. Review and apply any official patches or updates from ApostropheCMS once released.
CVE-2026-63669: CWE-639: Authorization Bypass Through User-Controlled Key in apostrophecms apostrophe
Description
ApostropheCMS versions prior to 4.32.0 contain an authorization bypass vulnerability in the page move operation. A regression in the move authorization guard disables the check that ensures a page can only be moved into a parent page the user has create rights over. This allows any authenticated user with edit rights on a page to move it under a restricted parent they lack create or edit permissions for. The move triggers an unchecked database update that re-ranks the restricted parent's children, potentially affecting documents the user cannot edit. The vulnerability is reachable via the documented REST API PATCH/PUT route with attacker-controlled parameters.
CVSS v3.1
Score 6.5medium
Affected software
apostrophecms
apostrophe
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
ApostropheCMS enforces per-type authorization on pages, including create and edit roles. The move() operation is intended to restrict moving pages only into parents where the user has create rights. However, a regression introduced in commit 9f72bd229be07e537a2ae894f4527f2fe6bcd3bd added a condition that gates the critical create permission check on the old parent being an archive page. For normal moves, this condition evaluates to false, effectively disabling the destination authorization check. Consequently, the only permission check is whether the user can edit the page being moved, which low-privileged editors can do for their own pages. This flaw allows moving pages under restricted parents without proper authorization. The move triggers an unguarded updateMany operation that re-ranks the restricted parent's children, modifying documents the user cannot edit. The vulnerability is exploitable via the documented REST API PATCH/PUT /api/v1/@apostrophecms/page/:_id route by controlling the _targetId and _position fields. The sibling insert route correctly enforces create permissions on the target, highlighting the regression in move().
Potential Impact
An authenticated user with edit rights on at least one page can bypass intended authorization controls to move that page under a restricted parent page they do not have create or edit permissions for. This unauthorized move triggers an unchecked database update that re-ranks the restricted parent's children, potentially modifying documents the user is not authorized to edit. The vulnerability does not disclose content or escalate privileges directly but allows unauthorized modification of page hierarchy and ordering, which may impact content integrity and access control enforcement.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict edit permissions to trusted users only and monitor for suspicious use of the page move API. Avoid exposing the PATCH/PUT /api/v1/@apostrophecms/page/:_id endpoint to untrusted users if possible. Review and apply any official patches or updates from ApostropheCMS once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-17T14:47:08.032Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a836787bf8831d5397b9a4a
Added to database: 08/17/2026, 19:56:55 UTC
Last enriched: 09/12/2026, 00:33:16 UTC
Last updated: 10/01/2026, 14:51:08 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.