CVE-2025-13924: CWE-352 Cross-Site Request Forgery (CSRF) in maartenbelmans Advanced Product Fields (Product Addons) for WooCommerce
The Advanced Product Fields (Product Addons) for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6.17. This is due to missing or incorrect nonce validation on the 'maybe_duplicate' function. This makes it possible for unauthenticated attackers to duplicate and publish product field groups, including draft and pending field groups, 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
The Advanced Product Fields (Product Addons) plugin for WooCommerce, widely used to extend product customization capabilities on WordPress e-commerce sites, contains a Cross-Site Request Forgery (CSRF) vulnerability identified as CVE-2025-13924. This vulnerability exists in all versions up to and including 1.6.17 due to missing or incorrect nonce validation in the 'maybe_duplicate' function, which handles duplication and publication of product field groups. Nonces are security tokens used to verify the legitimacy of requests, and their absence or improper implementation allows attackers to craft malicious requests that, when executed by an authenticated administrator, cause unintended actions such as duplicating and publishing product field groups, including those in draft or pending states. The attack vector requires no privileges or authentication by the attacker but depends on social engineering to convince an administrator to perform an action like clicking a specially crafted link. The impact is limited to integrity, as attackers can alter product configurations without direct access to sensitive data or system availability. The CVSS 3.1 base score is 4.3, reflecting low complexity of attack and user interaction requirement but no direct confidentiality or availability impact. No patches were linked at the time of publication, and no active exploits have been reported. This vulnerability highlights the importance of proper nonce validation in WordPress plugins to prevent CSRF attacks that leverage trusted user sessions.
Potential Impact
The primary impact of this vulnerability is on the integrity of e-commerce product configurations. An attacker can manipulate product field groups by duplicating and publishing them without authorization, potentially leading to incorrect product options being displayed or sold. This could cause confusion for customers, disrupt sales processes, or damage brand reputation. While the vulnerability does not expose sensitive customer data or disrupt site availability, unauthorized changes to product fields could indirectly affect business operations and customer trust. Since exploitation requires an administrator to be tricked into clicking a malicious link, the risk is mitigated by user awareness but remains significant in environments with multiple administrators or less security-conscious personnel. Organizations relying heavily on WooCommerce with this plugin installed are at risk of unauthorized product configuration changes, which could be leveraged as part of larger attacks or fraud schemes.
Mitigation Recommendations
Organizations should monitor for updates from the plugin vendor and apply patches promptly once released to address the nonce validation issue. Until a patch is available, administrators should be trained to recognize and avoid clicking suspicious links, especially those received via email or untrusted sources. Implementing web application firewalls (WAFs) with rules to detect and block CSRF attempts targeting the plugin's endpoints can reduce risk. Limiting administrative access to trusted personnel and enforcing multi-factor authentication (MFA) for admin accounts can further mitigate exploitation potential. Additionally, reviewing and restricting the use of plugins to only those necessary and maintaining a minimal attack surface on WordPress installations is recommended. Regular audits of product field groups and logs can help detect unauthorized changes early. Finally, developers should adopt secure coding practices including proper nonce validation for all state-changing actions in WordPress plugins.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-13924: CWE-352 Cross-Site Request Forgery (CSRF) in maartenbelmans Advanced Product Fields (Product Addons) for WooCommerce
Description
The Advanced Product Fields (Product Addons) for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6.17. This is due to missing or incorrect nonce validation on the 'maybe_duplicate' function. This makes it possible for unauthenticated attackers to duplicate and publish product field groups, including draft and pending field groups, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Advanced Product Fields (Product Addons) plugin for WooCommerce, widely used to extend product customization capabilities on WordPress e-commerce sites, contains a Cross-Site Request Forgery (CSRF) vulnerability identified as CVE-2025-13924. This vulnerability exists in all versions up to and including 1.6.17 due to missing or incorrect nonce validation in the 'maybe_duplicate' function, which handles duplication and publication of product field groups. Nonces are security tokens used to verify the legitimacy of requests, and their absence or improper implementation allows attackers to craft malicious requests that, when executed by an authenticated administrator, cause unintended actions such as duplicating and publishing product field groups, including those in draft or pending states. The attack vector requires no privileges or authentication by the attacker but depends on social engineering to convince an administrator to perform an action like clicking a specially crafted link. The impact is limited to integrity, as attackers can alter product configurations without direct access to sensitive data or system availability. The CVSS 3.1 base score is 4.3, reflecting low complexity of attack and user interaction requirement but no direct confidentiality or availability impact. No patches were linked at the time of publication, and no active exploits have been reported. This vulnerability highlights the importance of proper nonce validation in WordPress plugins to prevent CSRF attacks that leverage trusted user sessions.
Potential Impact
The primary impact of this vulnerability is on the integrity of e-commerce product configurations. An attacker can manipulate product field groups by duplicating and publishing them without authorization, potentially leading to incorrect product options being displayed or sold. This could cause confusion for customers, disrupt sales processes, or damage brand reputation. While the vulnerability does not expose sensitive customer data or disrupt site availability, unauthorized changes to product fields could indirectly affect business operations and customer trust. Since exploitation requires an administrator to be tricked into clicking a malicious link, the risk is mitigated by user awareness but remains significant in environments with multiple administrators or less security-conscious personnel. Organizations relying heavily on WooCommerce with this plugin installed are at risk of unauthorized product configuration changes, which could be leveraged as part of larger attacks or fraud schemes.
Mitigation Recommendations
Organizations should monitor for updates from the plugin vendor and apply patches promptly once released to address the nonce validation issue. Until a patch is available, administrators should be trained to recognize and avoid clicking suspicious links, especially those received via email or untrusted sources. Implementing web application firewalls (WAFs) with rules to detect and block CSRF attempts targeting the plugin's endpoints can reduce risk. Limiting administrative access to trusted personnel and enforcing multi-factor authentication (MFA) for admin accounts can further mitigate exploitation potential. Additionally, reviewing and restricting the use of plugins to only those necessary and maintaining a minimal attack surface on WordPress installations is recommended. Regular audits of product field groups and logs can help detect unauthorized changes early. Finally, developers should adopt secure coding practices including proper nonce validation for all state-changing actions in WordPress plugins.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-12-02T20:51:17.716Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69385e4c74ebaa3baba14004
Added to database: 12/9/2025, 5:37:16 PM
Last enriched: 2/27/2026, 10:33:24 AM
Last updated: 3/24/2026, 12:28:53 PM
Views: 86
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.