WordPress security changelog
MEDIUM CVE-2012-5387 Modified

White Label Cms: Cross-site scripting

White Label Cms is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

CVE / CNA score 6.8 CVSS · cve@mitre.org
NVD score 6.8 CVSS 2.0 · nvd@nist.gov
Component
White Label Cms
Plugin slug
white-label-cms
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 24, 2012
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Oct 24, 2012 and is one of 7 known issues for this plugin.

What to do

Update, patch or deactivate.

Update White Label Cms to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

Cross-site request forgery (CSRF) vulnerability in wlcms-plugin.php in the White Label CMS plugin before 1.5.1 for WordPress allows remote attackers to hijack the authentication of administrators for requests that modify the developer name via the wlcms_o_developer_name parameter in a save action to wp-admin/admin.php, as demonstrated by a developer name containing XSS sequences.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Primary and upstream sources