CVE-2026-31272
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMRCMS 3.1.2 contains an access control vulnerability. The save() method in src/main/java/org/marker/mushroom/controller/UserController.java lacks proper authorization validation, enabling direct addition of super administrator accounts without authentication.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMRCMS 3.1.2 has a critical access control vulnerability in the UserController's save() method which lacks authorization validation. This allows unauthenticated attackers to create super administrator accounts directly, achieving full application compromise without any credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MRCMS versionLocate the version file or header in the MRCMS installation (commonly version.php, or check the main index/bootstrap file for a $version or VERSION constant). Compare the installed version to 3.1.2.Affected if The installed version is exactly 3.1.2.
-
Locate UserController fileFind the UserController.php file in the application source code (typically in app/Http/Controllers or similar MVC directory structure).Affected if The UserController.php file exists in the application.
-
Inspect save() method for authorizationOpen UserController.php and examine the save() method. Search for authorization checks such as $this->authorize(), auth()->check(), middleware('auth'), or role/permission validation logic before user creation proceeds.Affected if The save() method contains no authorization, authentication, or role verification logic before processing user data.
-
Verify endpoint accessibilityAttempt to access the user creation endpoint (typically /user/save or /admin/user/store) using a tool like curl or Burp without providing any session cookie or authentication token.Affected if The endpoint responds without requiring authentication (returns 200 OK or accepts the request instead of redirecting to login or returning 401/403).
-
Check for super admin role creation capabilityIn the save() method, examine if the code allows setting a role parameter to a privileged value (such as 'super_admin', 'administrator', or role_id 1) without validation.Affected if The save() method accepts and processes a role parameter for creating privileged accounts without verifying the caller's permissions.
If MRCMS version is 3.1.2 AND the UserController save() method lacks authorization checks AND the endpoint accepts unauthenticated requests, the environment is vulnerable to unauthenticated super administrator account creation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and role-based authorization checks in the save() method before allowing user creation, particularly for privileged role assignments. Require session validation and verify the caller's permissions before executing account creation logic.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data