CVE-2024-6625 json
WP Total Branding <= 1.2 - Authenticated (Administrator+) Stored Cross-Site Scripting via title Parameter
published 2024-07-12 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-47684
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
The WP Total Branding – Complete branding solution for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- m_uysl WP Total Branding – Complete branding solution for WordPress
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3b6ac92f-2ad1-4528-b157-5e49d6f224a5?source=cve
- plugins.trac.wordpress.org /browser/wp-total-branding/trunk/includes/modules/login.php#L87
- plugins.trac.wordpress.org /changeset/3115880/wp-total-branding/trunk/includes/options/login.php
- plugins.trac.wordpress.org /changeset/3115880/wp-total-branding/trunk/includes/modules/login.php
- wordpress.org /plugins/wp-total-branding/#developers
Sources
- CVE List CVE-2024-6625
- NVD CVE-2024-6625
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.