VYPR
High severityNVD Advisory· Published Sep 5, 2019· Updated Aug 5, 2024

CVE-2019-15953

CVE-2019-15953

Description

Total.js CMS 12.0.0 fails to enforce access controls on API endpoints, allowing authenticated users with limited privileges to access unauthorized resources, leading to privilege escalation.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Total.js CMS 12.0.0 fails to enforce access controls on API endpoints, allowing authenticated users with limited privileges to access unauthorized resources, leading to privilege escalation.

Total.js CMS 12.0.0 suffers from a broken access control vulnerability where the system only enforces privilege checks on front-end resource paths, not on corresponding API requests [1]. This allows an authenticated user with limited privileges to directly call API endpoints that should be restricted.

To exploit this, an attacker must first authenticate with any user account, even one with minimal privileges (e.g., 'Notices'). By capturing the session cookie from the admin front-end and making a crafted POST request to an API endpoint such as /admin/api/pages/preview/, the attacker can receive a 200 response, indicating successful access to a resource they are not authorized to use [4]. No special network position is required; the attacker simply needs to be able to send HTTP requests to the CMS.

The impact includes both vertical and horizontal privilege escalation. A low-privileged user can access administrative functions or other users' data, potentially leading to full system compromise [1]. As of the disclosure timeline, the vendor was notified in February 2019 but had not released a patch by August 2019 [4]. Users should restrict network access to the CMS and apply any available updates.

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.