Summary
A broken access control vulnerability in Ghost 5.x allows authenticated users with the Author role to delete posts owned by other users. The issue becomes risky when an Author can reach post-deletion functionality without an effective ownership or authorization check.
Affected context
The vulnerability occurs in Ghost 5.x post authorization logic when the post model evaluates whether an authenticated Author may delete content. Deployments are exposed where Author accounts can access the affected deletion workflow and the permission decision does not correctly account for both the user's role and the destructive operation.
Exploit preconditions
- Attack surface: Ghost post-management and deletion functionality
- Required access: An authenticated Ghost account with the Author role
- Trigger point: Authorization evaluation for deleting a post owned by another user
- Why exploitation is possible: The permissible() authorization cascade lacks the branch for the combined Author and delete conditions, allowing the decision to fall through without enforcing ownership
Why this happens
The underlying bug is an incomplete authorization decision tree in the post model's permissible() logic. A condition that should have handled the combination of an Author role and a destructive operation was omitted, so authorization could fall through instead of requiring ownership or another permitted relationship. This maps to CWE-284, which covers failures to properly enforce access restrictions on protected resources.
Potential impact
- An Author may delete posts belonging to other users
- Content owners may experience unauthorized data loss
- Editorial workflows and publishing history could be disrupted
- The platform's content integrity and availability may be reduced
General mitigation guidance
Mitigation generally focuses on making authorization decisions explicit,
deny-by-default, and operation-specific.
Common defensive patterns include:
- Enforcing object ownership and role permissions for every destructive action
- Representing combined role-and-operation cases explicitly in authorization logic
- Applying centralized policy checks consistently across API and administrative paths
- Separating read, create, update, and delete permissions rather than relying on broad role access
- Revalidating authorization at the server-side operation boundary
- Running content-management services with least privilege and limiting administrative capabilities
- Adding regression tests for cross-user access attempts and negative authorization cases
How teams detect issues like this
Organizations can detect similar access-control weaknesses through:
- Static analysis for incomplete conditional branches and permissive fall-through behavior
- Code review checks requiring explicit authorization for every destructive operation
- Tests that attempt cross-user deletion with each supported role
- API monitoring for unusual deletion activity by Author accounts
- Policy enforcement requiring deny-by-default authorization and resource-level ownership checks
- Automated security testing or code-review tools that identify missing object-level access controls

