dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-9209

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-03
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 No privileges 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
The RestroPress – Online Food Ordering System plugin for WordPress is vulnerable to Authentication Bypass in versions 3.0.0 to 3.1.9.2. This is due to the plugin exposing user private tokens and API data via the /wp-json/wp/v2/users REST API endpoint. This makes it possible for unauthenticated attackers to forge JWT tokens for other users, including administrators, and authenticate as them.

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 confidence

The RestroPress WordPress plugin versions 3.0.0 to 3.1.9.2 exposes sensitive user data (private tokens and API credentials) through the /wp-json/wp/v2/users REST API endpoint without proper access controls. This allows unauthenticated attackers to retrieve these tokens and forge JWT authentication tokens, enabling full administrative access to the WordPress site.

MitigationUpdate RestroPress to version 3.1.9.3 or later which patches the authentication bypass. Alternatively, disable the plugin until an update is available or restrict REST API user endpoint access at the server level.

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
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 checks

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

  1. Confirm RestroPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'restropress'
    Affected if The RestroPress plugin is present in the WordPress installation
  2. Identify installed RestroPress version
    Check the plugin version in the WordPress Plugins admin page, or open the main plugin file (e.g., restropress.php) and look for the version header comment, or inspect restropress/readme.txt for the Stable tag
    Affected if The installed version falls within 3.0.0 through 3.1.9.2 (inclusive)
  3. Test unauthenticated REST API user endpoint access
    Send a GET request to https://yourdomain.com/wp-json/wp/v2/users (or curl -s https://yourdomain.com/wp-json/wp/v2/users) without providing any authentication credentials
    Affected if The endpoint returns user data (array of user objects) with HTTP 200 status instead of 401 (unauthorized) or 403 (forbidden)
  4. Check for sensitive data in user endpoint response
    Inspect the JSON response from the /wp-json/wp/v2/users endpoint for fields containing tokens, API keys, credentials, or other sensitive user metadata
    Affected if The response includes private tokens, API credentials, or other sensitive data in user objects accessible to unauthenticated requests

A user is affected if RestroPress versions 3.0.0-3.1.9.2 are installed AND the /wp-json/wp/v2/users endpoint is publicly accessible without authentication, exposing sensitive user data.

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

Update RestroPress to version 3.1.9.3 or later which patches the authentication bypass. Alternatively, disable the plugin until an update is available or restrict REST API user endpoint access at the server level.

Recommended fix High confidence

Version 3.1.9.3 or later (any version beyond 3.1.9.2)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate RestroPress – Online Food Ordering System plugin
  4. Check the current version number displayed under the plugin name
  5. If the installed version is 3.1.9.2 or lower, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and apply any available updates
  7. After updating, verify the new version number in the plugins list
  8. Test that the /wp-json/wp/v2/users endpoint no longer exposes sensitive token data for unauthenticated requests

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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