/

CVE-2026-31272

Severity:

CRITICAL RISK

(9.8)

Broken Access Control in MRCMS User Management Controller

CVE-2026-31272

Analyzed

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Privilege Escalation to Super Administrator / Full Application Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MRCMS 3.1.2 exposes a critical broken access control issue in the UserController.save() method, which lacks proper authorization checks.

An attacker can directly invoke this endpoint to create super administrator accounts without any authentication, effectively bypassing the normal privilege model and taking over the system.

Affected context

This vulnerability occurs in MRCMS 3.1.2 within the user management functionality, specifically in the UserController.save() method.

It is relevant when the application is deployed with its default routing and no additional external access controls blocking direct HTTP requests to administrative endpoints.

Environments where the management interface is reachable from untrusted networks are particularly exposed, as the flawed method can be called without going through any authentication or role verification.

Exploit preconditions

  • Attack surface: HTTP(S) endpoint exposing the user creation functionality in MRCMS.
  • Required access: Network access to the MRCMS instance (e.g., ability to send requests to the web application).
  • Trigger point: Direct invocation of the save() method endpoint responsible for creating or modifying users.
  • Why exploitation is possible: The controller method does not enforce authentication or authorization checks before allowing creation of a super administrator account, so any caller can submit a crafted request that results in privileged account creation.

Why this happens

The underlying issue is a broken access control pattern where a security-sensitive operation—creating super administrator accounts—is implemented without authorization enforcement.

The UserController.save() method omits checks to verify that the caller is authenticated and has sufficient privileges to perform user creation or role assignment.

This maps to CWE-284: Improper Access Control, where the system fails to enforce restrictions on what actions users (or unauthenticated clients) are allowed to perform, placing critical administrative functionality directly on an unprotected endpoint.

Potential impact

  • Creation of arbitrary super administrator accounts that can control the entire MRCMS instance
  • Full compromise of site content, configuration, and user data
  • Installation of backdoors or malicious plugins through the administrative interface
  • Tampering with access controls, logs, and security settings to hide further malicious activity
  • Use of the compromised CMS as a platform for phishing, malware distribution, or defacement

General mitigation guidance

Mitigation centers on enforcing strict, role-aware access control on all administrative operations.

Recommended patterns include:

  • Applying mandatory authentication and authorization checks in all controller methods that create, modify, or delete user accounts or roles.
  • Centralizing access control logic (e.g., using annotations, filters, or middleware) so that administrative endpoints cannot accidentally bypass checks.
  • Enforcing role-based access control (RBAC) with a clear policy that only existing high-privilege administrators can create or grant super administrator roles.
  • Treating super administrator creation as a rare, high-risk operation that may require additional confirmation or out-of-band controls.
  • Limiting network exposure of administrative interfaces (for example, restricting to management networks or VPN-only access) to reduce the reachable attack surface.

How teams detect issues like this

Effective detection combines code-level review and runtime monitoring:

  • Static analysis: Configure rules to flag controller methods that modify user accounts or roles when they lack explicit authentication/authorization annotations or checks.
  • Code review: During reviews, scrutinize user management, role assignment, and administrative controllers for missing access control enforcement and for direct role elevation logic.
  • Security testing: Perform targeted authorization testing in QA or staging environments to verify that administrative endpoints cannot be reached or exercised by unauthenticated or low-privilege users.
  • Logging and monitoring: Instrument administrative account creation and role changes with high-integrity logs and alerts that surface unexpected or unusual privilege-granting actions.

Sources

SourceLink
github.comgithub.com/clockw1se0v0/Vul/blob/main/MRCMS/Unauthorized.md

Frequently asked

questions

Yes. If the MRCMS instance is reachable over a network, an attacker can remotely invoke the vulnerable endpoint to create a super administrator account, without needing any prior access.

No. The core issue is the lack of authentication and authorization in the UserController.save() method, which allows unauthenticated clients to perform privileged user creation.

The safest approach is to enforce strict authentication and role-based authorization on all user management methods, ensuring that only already-authenticated high-privilege administrators can create or modify administrative accounts, particularly super administrators.

Adopt a secure development pattern where all administrative and user-management endpoints are protected by centralized access control mechanisms, backed by automated tests and code scanning rules that fail builds when sensitive operations lack explicit authorization checks.

Find out what's already
exploitable in your codebase.