Add Any Extension to Pages <= 1.4 - Cross-Site Request Forgery via aaetp_options_page
Strategic Overview
- Status
- Patched in 1.5
- Affected Plugin
- Add Any Extension to Pages
- Affected Version
<= 1.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-50873
At a glance
CVE-2023-50873 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Add Any Extension to Pages WordPress plugin, affecting versions <= 1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.5; sites on affected versions should update now. Disclosed December 2023, reported by Nguyen Xuan Chien.
Vulnerability Overview
The Add Any Extension to Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the 'aaetp_options_page' function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Add Any Extension to Pages <= 1.4 carries this weakness at aaetp_options_page, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Add Any Extension to Pages the fix is 1.5: builds <= 1.4 are affected, anything from 1.5 onward is not.
Remediation
Update to version 1.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Add Any Extension to Pages: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Add Any Extension to Pages 1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Add Any Extension to Pages
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C