Developer Formatter < 2013.0.1.41 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2013.0.1.41
- Affected Plugin
- Developer Formatter
- Affected Version
< 2013.0.1.41- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Developer Formatter WordPress plugin, affecting versions < 2013.0.1.41. 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 2013.0.1.41; sites on affected versions should update now. Disclosed January 2013, reported by Junaid Hussain.
Vulnerability Overview
The Developer Formatter plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 2013.0.1.41. This is due to missing or incorrect nonce validation on the devfmt_addPage() function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious web scripts 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)
Developer Formatter < 2013.0.1.41 carries this weakness at devfmt_addPage(), 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 Developer Formatter the fix is 2013.0.1.41: builds < 2013.0.1.41 are affected, anything from 2013.0.1.41 onward is not.
Remediation
Update to version 2013.0.1.41, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Developer Formatter: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Developer Formatter 2013.0.1.41 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Developer Formatter
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C