CVE-2025-10173: CWE-862 Missing Authorization in roxnor ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution
The ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution plugin for WordPress is vulnerable to unauthorized access due to an incorrect capability check on the post_save() function in all versions up to, and including, 4.8.3. This makes it possible for authenticated attackers, with Editor-level access and above, to update the plugin's settings.
AI Analysis
Technical Summary
CVE-2025-10173 identifies a missing authorization vulnerability (CWE-862) in the ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution plugin for WordPress, affecting all versions up to and including 4.8.3. The vulnerability stems from an improper capability check within the post_save() function, which is responsible for saving plugin settings. This flaw allows any authenticated user with Editor-level access or higher to update the plugin's settings without proper authorization. Since Editors typically have broad content editing permissions but not full administrative rights, this vulnerability effectively elevates their privileges within the plugin context, potentially leading to unauthorized configuration changes. The vulnerability is remotely exploitable over the network without requiring user interaction, but it requires the attacker to be authenticated with sufficient privileges. The CVSS v3.1 base score is 2.7, reflecting low severity due to limited impact on confidentiality and availability, with only integrity affected. No public exploits or patches are currently available, and the vulnerability was published on September 26, 2025. The issue is significant because WooCommerce is widely used for e-commerce on WordPress, and ShopEngine is a popular addon for building WooCommerce stores, meaning many sites could be exposed if they use this plugin version and have multiple Editors.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of plugin settings by users with Editor-level privileges or higher. While this does not directly expose sensitive data or cause service disruption, unauthorized changes to plugin configurations could lead to misconfigurations that degrade site functionality, introduce further security weaknesses, or disrupt e-commerce operations. For example, attackers could alter payment settings, product display options, or other critical parameters, potentially affecting business operations or customer experience. The scope is limited to sites running the vulnerable plugin version and having users with Editor or higher roles. Since Editors are common in content management workflows, this vulnerability could be exploited internally or by compromised accounts. The lack of known exploits reduces immediate risk, but the widespread use of WooCommerce and WordPress globally means many organizations could be affected if the vulnerability is weaponized. Overall, the impact is low but could be more severe in environments with lax role management or high-value e-commerce operations.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first update the ShopEngine Elementor WooCommerce Builder Addon plugin to a version that addresses the missing authorization check once available. In the absence of an official patch, administrators should restrict Editor-level privileges to trusted users only and review user roles to minimize the number of users with elevated permissions. Implementing strict role-based access control (RBAC) and monitoring changes to plugin settings can help detect unauthorized modifications. Additionally, applying the principle of least privilege by limiting Editor capabilities or temporarily downgrading users who do not require such access can reduce risk. Web application firewalls (WAFs) may be configured to detect anomalous requests targeting plugin settings endpoints. Regular security audits and monitoring of WordPress logs for unusual activity related to plugin configuration changes are recommended. Finally, educating site administrators and editors about the risks of privilege misuse can further reduce exploitation likelihood.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-10173: CWE-862 Missing Authorization in roxnor ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution
Description
The ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution plugin for WordPress is vulnerable to unauthorized access due to an incorrect capability check on the post_save() function in all versions up to, and including, 4.8.3. This makes it possible for authenticated attackers, with Editor-level access and above, to update the plugin's settings.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-10173 identifies a missing authorization vulnerability (CWE-862) in the ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution plugin for WordPress, affecting all versions up to and including 4.8.3. The vulnerability stems from an improper capability check within the post_save() function, which is responsible for saving plugin settings. This flaw allows any authenticated user with Editor-level access or higher to update the plugin's settings without proper authorization. Since Editors typically have broad content editing permissions but not full administrative rights, this vulnerability effectively elevates their privileges within the plugin context, potentially leading to unauthorized configuration changes. The vulnerability is remotely exploitable over the network without requiring user interaction, but it requires the attacker to be authenticated with sufficient privileges. The CVSS v3.1 base score is 2.7, reflecting low severity due to limited impact on confidentiality and availability, with only integrity affected. No public exploits or patches are currently available, and the vulnerability was published on September 26, 2025. The issue is significant because WooCommerce is widely used for e-commerce on WordPress, and ShopEngine is a popular addon for building WooCommerce stores, meaning many sites could be exposed if they use this plugin version and have multiple Editors.
Potential Impact
The primary impact of this vulnerability is the unauthorized modification of plugin settings by users with Editor-level privileges or higher. While this does not directly expose sensitive data or cause service disruption, unauthorized changes to plugin configurations could lead to misconfigurations that degrade site functionality, introduce further security weaknesses, or disrupt e-commerce operations. For example, attackers could alter payment settings, product display options, or other critical parameters, potentially affecting business operations or customer experience. The scope is limited to sites running the vulnerable plugin version and having users with Editor or higher roles. Since Editors are common in content management workflows, this vulnerability could be exploited internally or by compromised accounts. The lack of known exploits reduces immediate risk, but the widespread use of WooCommerce and WordPress globally means many organizations could be affected if the vulnerability is weaponized. Overall, the impact is low but could be more severe in environments with lax role management or high-value e-commerce operations.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first update the ShopEngine Elementor WooCommerce Builder Addon plugin to a version that addresses the missing authorization check once available. In the absence of an official patch, administrators should restrict Editor-level privileges to trusted users only and review user roles to minimize the number of users with elevated permissions. Implementing strict role-based access control (RBAC) and monitoring changes to plugin settings can help detect unauthorized modifications. Additionally, applying the principle of least privilege by limiting Editor capabilities or temporarily downgrading users who do not require such access can reduce risk. Web application firewalls (WAFs) may be configured to detect anomalous requests targeting plugin settings endpoints. Regular security audits and monitoring of WordPress logs for unusual activity related to plugin configuration changes are recommended. Finally, educating site administrators and editors about the risks of privilege misuse can further reduce exploitation likelihood.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-09T14:06:52.606Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68d60d329e21be37e93b46fd
Added to database: 9/26/2025, 3:49:06 AM
Last enriched: 2/27/2026, 6:12:56 PM
Last updated: 3/24/2026, 7:47:18 AM
Views: 168
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 more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.