Cross-site scripting (XSS) vulnerability in wp-includes/wp-db.php in WordPress before 4.2.1 allows remote attackers to…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is a cross-site scripting (XSS) vulnerability in wp-includes/wp-db.php, a component of WordPress before 4.2.1. An attacker can inject arbitrary web script or HTML by submitting a long comment that is improperly stored because of limitations of the MySQL TEXT data type, and no specific authentication, user interaction, or configuration requirements are stated in the available data.
Official description · CVE.org
Cross-site scripting (XSS) vulnerability in wp-includes/wp-db.php in WordPress before 4.2.1 allows remote attackers to inject arbitrary web script or HTML via a long comment that is improperly stored because of limitations on the MySQL TEXT data type.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 3 months before it was disclosed. Public exploit code (Exploit-DB) was available 3 months before disclosure.
- Disclosedday 0
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
A fix was bypassed or incomplete once over 10 months.
Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.
- This CVECVE-2015-3440Cross-site scripting (XSS) vulnerability in…3 Aug 2015
incomplete fixHigh
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Stated in the CVE text
NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-3440.
- Stated in the CVE text