dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-4514

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A flaw has been found in PbootCMS up to 3.2.12. Affected by this issue is some unknown functionality of the file apps/admin/controller/system/UserController.php of the component Backend. Executing a manipulation of the argument Field can lead to improper access controls. The attack may be performed from remote. The exploit has been published and may be used.

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 · moderate confidence

PbootCMS up to version 3.2.12 contains an improper access control vulnerability in the Backend UserController.php file. The Field parameter handling lacks proper authorization checks, allowing remote attackers to potentially bypass access controls and perform unauthorized operations in the admin interface.

MitigationUpgrade PbootCMS to a version beyond 3.2.12 that contains the security patch. If no patched version is available, implement web application firewall rules to restrict access to the admin endpoints and verify that authentication is properly enforced on all UserController methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PbootCMS version
    Locate the version file in the PbootCMS installation (commonly in /core/function/helper.php or displayed in the backend footer). Compare the version number to the affected range (3.2.12 and below).
    Affected if The installed version is 3.2.12 or lower
  2. Locate the UserController.php file
    Find the UserController.php file in the backend directory structure, typically at /apps/admin/controller/system/UserController.php or similar path under the admin folder.
    Affected if The file exists in the installation
  3. Verify the Field parameter handling lacks authorization
    Examine the UserController.php code, specifically looking at methods that handle the 'Field' parameter. Check if there are proper authorization checks (such as session validation, permission checks, or admin authentication) before processing the Field parameter in any method.
    Affected if The Field parameter is processed without visible authorization checks in any UserController method
  4. Test admin endpoint accessibility
    Attempt to access admin interface endpoints (such as /admin.php/User/ or similar) without valid authentication credentials. Check if the application returns admin functionality or authorization errors.
    Affected if Admin endpoints are accessible or return partial functionality without proper authentication
  5. Check for authentication enforcement on all UserController methods
    Review the UserController.php code and verify that every public method contains proper authentication validation (e.g., check for session admin login status, permission role validation, or middleware/auth decorators).
    Affected if Any UserController method lacks proper authentication enforcement

A user is affected if PbootCMS version 3.2.12 or lower is installed AND the admin interface or UserController endpoints are accessible without proper authorization, particularly where the Field parameter is handled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade PbootCMS to a version beyond 3.2.12 that contains the security patch. If no patched version is available, implement web application firewall rules to restrict access to the admin endpoints and verify that authentication is properly enforced on all UserController methods.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4514 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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