WP-Orphanage Extended <= 1.2 - Cross-Site Request Forgery to Orphan Account Privilege Escalation
Strategic Overview
- Status
- Patched in 1.3
- Affected Plugin
- WP-Orphanage Extended
- Affected Version
<= 1.2- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-11415
At a glance
CVE-2024-11415 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP-Orphanage Extended WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3; sites on affected versions should update now. Disclosed November 2024, reported by SOPROBRO.
Vulnerability Overview
The WP-Orphanage Extended plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the wporphanageex_menu_settings() function. This makes it possible for unauthenticated attackers to escalate the privileges of all orphan accounts 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
WP-Orphanage Extended <= 1.2 carries this weakness at wporphanageex_menu_settings(), 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 WP-Orphanage Extended the fix is 1.3: builds <= 1.2 are affected, anything from 1.3 onward is not.
Remediation
Update to version 1.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-Orphanage Extended: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-Orphanage Extended 1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C