Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9209: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in magnigenie RestroPress – Online Food Ordering System

0
Critical
VulnerabilityCVE-2025-9209cvecve-2025-9209cwe-200
Published: Fri Oct 03 2025 (10/03/2025, 11:17:09 UTC)
Source: CVE Database V5
Vendor/Project: magnigenie
Product: RestroPress – Online Food Ordering System

Description

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.

AI-Powered Analysis

AILast updated: 10/03/2025, 11:25:26 UTC

Technical Analysis

CVE-2025-9209 is a critical vulnerability affecting the RestroPress – Online Food Ordering System plugin for WordPress, specifically versions 3.0.0 through 3.1.9.2. This vulnerability arises from an authentication bypass caused by the exposure of sensitive user data through the /wp-json/wp/v2/users REST API endpoint. The plugin inadvertently leaks private tokens and API data, which are intended to be confidential. Because of this exposure, unauthenticated attackers can retrieve these tokens and subsequently forge JSON Web Tokens (JWTs) for arbitrary users, including those with administrative privileges. This effectively allows attackers to authenticate as any user without needing valid credentials or user interaction. The vulnerability is classified under CWE-200, indicating exposure of sensitive information to unauthorized actors. The CVSS v3.1 base score is 9.8, reflecting its critical severity, with attack vector being network-based, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. Although no public exploits are currently known, the ease of exploitation and the high impact make this vulnerability a significant threat to any WordPress site using the affected plugin versions. Attackers could leverage this flaw to gain full control over the affected WordPress installation, manipulate orders, steal customer data, or disrupt service availability, severely compromising the online food ordering system's security and trustworthiness.

Potential Impact

For European organizations, especially those operating in the food service and hospitality sectors using WordPress with the RestroPress plugin, this vulnerability poses a severe risk. Exploitation could lead to unauthorized access to sensitive customer data, including personal and payment information, violating GDPR and other data protection regulations. The ability to impersonate administrators could allow attackers to alter order data, inject malicious content, or disrupt business operations, leading to financial losses and reputational damage. Given the critical nature of the vulnerability, organizations may face regulatory penalties and loss of customer trust. Additionally, since the vulnerability affects a plugin commonly used in e-commerce contexts, the potential for fraud, data theft, and service disruption is high. The impact extends beyond individual businesses to the broader supply chain and customer base, potentially affecting multiple stakeholders across Europe.

Mitigation Recommendations

Immediate mitigation involves updating the RestroPress plugin to a patched version once released by the vendor. Until a patch is available, organizations should implement the following specific measures: 1) Restrict access to the /wp-json/wp/v2/users REST API endpoint by configuring web application firewalls (WAFs) or server-level access controls to allow only authenticated and authorized users; 2) Employ strict role-based access controls within WordPress to minimize the number of users with administrative privileges; 3) Monitor logs for unusual API access patterns or token generation activities indicative of exploitation attempts; 4) Disable or limit REST API access where feasible, especially for unauthenticated users; 5) Use security plugins that can detect and block suspicious JWT token usage; 6) Conduct regular security audits and penetration testing focused on REST API endpoints; 7) Educate staff on the risks and signs of compromise related to this vulnerability. These targeted steps go beyond generic advice by focusing on controlling REST API exposure and monitoring JWT token misuse.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-08-19T18:58:41.894Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68dfb275c3835a5fbe033c48

Added to database: 10/3/2025, 11:24:37 AM

Last enriched: 10/3/2025, 11:25:26 AM

Last updated: 10/7/2025, 10:04:02 AM

Views: 39

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats