CVE-2025-9209

RestroPress – Online Food Ordering System 3.0.0 - 3.2.1 - Unauthenticated Information Exposure to Authentication Bypass via Forged JWT

2025-10-02 22:17
kr0d

Strategic Overview

Status
Patched in 3.2.2
Affected Plugin
RestroPress – Online Food Ordering System
Affected Version
3.0.0 – 3.2.1
CVSS
9.8Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-9209
View all RestroPress – Online Food Ordering System vulnerabilities

At a glance

CVE-2025-9209 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the RestroPress WordPress plugin, affecting versions 3.0.0 – 3.2.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.2; sites on affected versions should update now. Disclosed October 2025, reported by kr0d.

Vulnerability Overview

The RestroPress – Online Food Ordering System plugin for WordPress is vulnerable to Authentication Bypass in versions 3.0.0 to 3.2.1. 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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in RestroPress 3.0.0 – 3.2.1 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For RestroPress the fix is 3.2.2: builds 3.0.0 – 3.2.1 are affected, anything from 3.2.2 onward is not.

Remediation

Update to version 3.2.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: RestroPress 3.2.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-9209https://www.wordfence.com/threat-intel/vulnerabilities/id/359833dd-de3c-48ea-8eef-06588a590da2https://nvd.nist.gov/vuln/detail/CVE-2025-9209

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C