CVE-2025-6214: CWE-352 Cross-Site Request Forgery (CSRF) in omnishop Omnishop – Mobile shop apps complementing your WooCommerce webshop
The Omnishop plugin for WordPress is vulnerable to Cross-Site Request Forgery on its /users/delete REST route in all versions up to, and including, 1.0.9. The route’s permission_callback only verifies that the requester is logged in, but fails to require any nonce or other proof of intent. This makes it possible for unauthenticated attackers to delete arbitrary user accounts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-6214 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the Omnishop WordPress plugin, which complements WooCommerce webshops by providing mobile shop apps. The vulnerability exists in the /users/delete REST API endpoint, present in all versions up to and including 1.0.9. The core issue lies in the permission_callback implementation, which only verifies that the requester is logged in but does not require any nonce or other proof of intent to validate the request's legitimacy. This design flaw allows an attacker to craft a malicious request that, if executed by an authenticated administrator (or any user with sufficient privileges), can delete arbitrary user accounts without their explicit consent. The attack vector requires the attacker to trick a logged-in administrator into clicking a malicious link or visiting a crafted webpage, which then silently triggers the deletion request. The vulnerability does not impact confidentiality or availability directly but severely impacts integrity by allowing unauthorized deletion of user accounts. The CVSS v3.1 base score is 6.5 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required for the attacker, but user interaction is necessary. No known exploits are currently reported in the wild, and no official patches have been linked yet. This vulnerability is significant because it targets a popular e-commerce plugin integrated with WooCommerce, widely used in WordPress-based online shops, potentially disrupting user management and causing operational issues for affected sites.
Potential Impact
For European organizations operating WooCommerce webshops using the Omnishop plugin, this vulnerability poses a risk of unauthorized user account deletions, which can disrupt business operations, customer management, and trust. The deletion of user accounts could lead to loss of customer data, interruption of order processing, and potential reputational damage. Since the vulnerability requires an administrator to be tricked into clicking a malicious link, targeted phishing campaigns could be used against European e-commerce administrators. This could be particularly impactful for small to medium-sized enterprises (SMEs) that may lack advanced security awareness or mitigation controls. Additionally, GDPR compliance could be affected if user data is improperly deleted or manipulated without proper authorization, leading to potential regulatory scrutiny. The vulnerability does not directly expose sensitive data but compromises the integrity of user management, which is critical for maintaining secure e-commerce operations.
Mitigation Recommendations
1. Immediate mitigation should include restricting access to the /users/delete REST endpoint by implementing strict nonce verification or other anti-CSRF tokens to ensure proof of intent for sensitive actions. 2. Administrators should be trained to recognize and avoid phishing attempts that could trick them into clicking malicious links. 3. Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable endpoint. 4. Limit administrator privileges and consider using multi-factor authentication (MFA) to reduce the risk of compromised admin sessions. 5. Monitor logs for unusual user deletion activities and set up alerts for unexpected REST API calls to the /users/delete route. 6. Regularly update the Omnishop plugin once a patch is released; meanwhile, consider disabling or restricting the plugin if feasible. 7. Employ Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks. 8. Conduct periodic security audits of WordPress plugins and REST API endpoints to identify and remediate similar vulnerabilities proactively.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-6214: CWE-352 Cross-Site Request Forgery (CSRF) in omnishop Omnishop – Mobile shop apps complementing your WooCommerce webshop
Description
The Omnishop plugin for WordPress is vulnerable to Cross-Site Request Forgery on its /users/delete REST route in all versions up to, and including, 1.0.9. The route’s permission_callback only verifies that the requester is logged in, but fails to require any nonce or other proof of intent. This makes it possible for unauthenticated attackers to delete arbitrary user accounts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Technical Analysis
CVE-2025-6214 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the Omnishop WordPress plugin, which complements WooCommerce webshops by providing mobile shop apps. The vulnerability exists in the /users/delete REST API endpoint, present in all versions up to and including 1.0.9. The core issue lies in the permission_callback implementation, which only verifies that the requester is logged in but does not require any nonce or other proof of intent to validate the request's legitimacy. This design flaw allows an attacker to craft a malicious request that, if executed by an authenticated administrator (or any user with sufficient privileges), can delete arbitrary user accounts without their explicit consent. The attack vector requires the attacker to trick a logged-in administrator into clicking a malicious link or visiting a crafted webpage, which then silently triggers the deletion request. The vulnerability does not impact confidentiality or availability directly but severely impacts integrity by allowing unauthorized deletion of user accounts. The CVSS v3.1 base score is 6.5 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required for the attacker, but user interaction is necessary. No known exploits are currently reported in the wild, and no official patches have been linked yet. This vulnerability is significant because it targets a popular e-commerce plugin integrated with WooCommerce, widely used in WordPress-based online shops, potentially disrupting user management and causing operational issues for affected sites.
Potential Impact
For European organizations operating WooCommerce webshops using the Omnishop plugin, this vulnerability poses a risk of unauthorized user account deletions, which can disrupt business operations, customer management, and trust. The deletion of user accounts could lead to loss of customer data, interruption of order processing, and potential reputational damage. Since the vulnerability requires an administrator to be tricked into clicking a malicious link, targeted phishing campaigns could be used against European e-commerce administrators. This could be particularly impactful for small to medium-sized enterprises (SMEs) that may lack advanced security awareness or mitigation controls. Additionally, GDPR compliance could be affected if user data is improperly deleted or manipulated without proper authorization, leading to potential regulatory scrutiny. The vulnerability does not directly expose sensitive data but compromises the integrity of user management, which is critical for maintaining secure e-commerce operations.
Mitigation Recommendations
1. Immediate mitigation should include restricting access to the /users/delete REST endpoint by implementing strict nonce verification or other anti-CSRF tokens to ensure proof of intent for sensitive actions. 2. Administrators should be trained to recognize and avoid phishing attempts that could trick them into clicking malicious links. 3. Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable endpoint. 4. Limit administrator privileges and consider using multi-factor authentication (MFA) to reduce the risk of compromised admin sessions. 5. Monitor logs for unusual user deletion activities and set up alerts for unexpected REST API calls to the /users/delete route. 6. Regularly update the Omnishop plugin once a patch is released; meanwhile, consider disabling or restricting the plugin if feasible. 7. Employ Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks. 8. Conduct periodic security audits of WordPress plugins and REST API endpoints to identify and remediate similar vulnerabilities proactively.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-06-17T21:08:02.919Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68804d50ad5a09ad00065fe1
Added to database: 7/23/2025, 2:47:44 AM
Last enriched: 7/23/2025, 3:03:50 AM
Last updated: 10/21/2025, 3:41:20 AM
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.