Strix
26.1K

CVE-2012-5387

UnknownEPSS 2.99%

Last modified

CVE-2012-5387 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.99% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
2.99%

85.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
VideousermanualsWhite-Label-Cms<= 1.5
VideousermanualsWhite-Label-Cms1.0.2
VideousermanualsWhite-Label-Cms1.0.3
VideousermanualsWhite-Label-Cms1.0.4
VideousermanualsWhite-Label-Cms1.0.5
VideousermanualsWhite-Label-Cms1.1
VideousermanualsWhite-Label-Cms1.2
VideousermanualsWhite-Label-Cms1.3
VideousermanualsWhite-Label-Cms1.4
VideousermanualsWhite-Label-Cms1.4.1
VideousermanualsWhite-Label-Cms1.4.2
VideousermanualsWhite-Label-Cms1.4.3
VideousermanualsWhite-Label-Cms1.4.4
VideousermanualsWhite-Label-Cms1.4.5
VideousermanualsWhite-Label-Cms1.4.6
VideousermanualsWhite-Label-Cms1.4.7

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2012-5387?
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.
How severe is CVE-2012-5387?
Severity scoring for CVE-2012-5387 is pending analysis. The EPSS model estimates a 2.99% probability of exploitation in the next 30 days.
How do I fix CVE-2012-5387?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2012-5387?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST