dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-54049

CRITICAL · 9.9 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Incorrect Privilege Assignment vulnerability in miniOrange Custom API for WP custom-api-for-wp allows Privilege Escalation.This issue affects Custom API for WP: from n/a through <= 4.2.2.

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

A critical privilege escalation vulnerability in the miniOrange Custom API for WP WordPress plugin allows authenticated users to gain elevated privileges beyond their intended access level. The 'Incorrect Privilege Assignment' weakness enables attackers to bypass role-based access controls, potentially allowing subscriber-level users to execute administrative functions through the custom API endpoints.

MitigationUpgrade the Custom API for WP plugin to the latest version immediately (check vendor advisories for 4.2.3+); if no patched version is available, disable the plugin until a fix is released.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

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

  1. Verify miniOrange Custom API for WP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Custom API for WP' or 'miniOrange'. Alternatively, check the /wp-content/plugins/ directory for folders containing 'custom-api' or 'mo' in the name.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list to view details, which typically displays the version number. Alternatively, check the main plugin file (usually in wp-content/plugins/custom-api-for-wp/ or similar) for the 'Version' header in the plugin comments.
    Affected if Unable to determine version or version is unknown/unpatched
  3. Confirm custom API endpoints are configured
    Look for custom API endpoint settings in the WordPress admin menu under the plugin's settings page (often labeled 'Custom API' or 'API Settings'). Check for any custom endpoints that may have been created.
    Affected if Custom API endpoints have been created and are active in the configuration
  4. Review user role and capability assignments
    Navigate to the plugin's role/capability management section (if available) and examine which roles have been granted elevated capabilities through the custom API feature. Check if subscriber-level users have been assigned capabilities beyond their standard permissions.
    Affected if Subscriber or low-privilege users have elevated capabilities assigned through the plugin settings
  5. Audit registered API endpoints accessible to authenticated users
    Use a tool like WP REST API browser or check the plugin's endpoint registration to identify accessible routes. Test whether unauthenticated or low-privilege authenticated requests can access admin-level functions.
    Affected if API endpoints exist that allow subscriber-level users to access administrative functions

If the miniOrange Custom API for WP plugin is installed with custom endpoints enabled and subscriber-level users have been granted elevated privileges through the plugin, the environment is likely affected by this privilege escalation vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Custom API for WP plugin to the latest version immediately (check vendor advisories for 4.2.3+); if no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Upgrade to Custom API for WP version 4.2.3 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Custom API for WP' (miniOrange) plugin
  4. 4. Check the current installed version (should be <= 4.2.2)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful and the new version is >= 4.2.3
  7. 7. Test that custom API endpoints function correctly after the update
Caveat Review plugin changelog for any breaking changes between 4.2.2 and the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54049 — 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-2025-54049 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