White Label CMS <= 1.5.2 - Cross-Site Request Forgery leading to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.5.3
- Affected Plugin
- White Label CMS
- Affected Version
< 1.5.3- CVSS
- 4.7Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the White Label CMS WordPress plugin, affecting versions < 1.5.3. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 1.5.3; sites on affected versions should update now. Disclosed April 2015, reported by James Hooker.
Vulnerability Overview
The White Label CMS plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.2. This is due to missing or incorrect nonce validation on the 'wlcmsImport' function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via 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, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
White Label CMS < 1.5.3 carries this weakness at wlcmsImport, 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 White Label CMS the fix is 1.5.3: builds < 1.5.3 are affected, anything from 1.5.3 onward is not.
Remediation
Update to version 1.5.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to White Label CMS: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: White Label CMS 1.5.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in White Label CMS
- 7.2CVE-2022-4302: White Label CMS <= 2.4 PHP Object Injection
CVE-2022-4302 - 7.1CVE-2012-5387: White Label CMS < 1.5.1 Reflected Cross-Site Scripting
CVE-2012-5387 - 7.1CVE-2012-5388: White Label CMS < 1.5.1 Cross-Site Scripting
CVE-2012-5388 - 6.1CVE-2024-43303: White Label CMS <= 2.7.4 Reflected XSS
CVE-2024-43303 - 6.1CVE-2022-0422: White Label MS <= 2.2.8 Reflected Cross-Site Scripting
CVE-2022-0422 - 5.3CVE-2024-4280: White Label CMS <= 2.7.3 Plugin Settings Reset
CVE-2024-4280 - 4.4CVE-2026-11898: White Label CMS <= 2.7.12 Stored Cross-Site Scripting
CVE-2026-11898
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C