Skip to content
Fencer Intel
medium 4.3

CVE-2015-3438 json

Multiple cross-site scripting (XSS) vulnerabilities in WordPress before 4.1.2, when MySQL is used without strict mode, allow remote attacke…

published 2015-08-05 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-3482

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.4%
EPSS 7.4% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Multiple cross-site scripting (XSS) vulnerabilities in WordPress before 4.1.2, when MySQL is used without strict mode, allow remote attackers to inject arbitrary web script or HTML via a (1) four-byte UTF-8 character or (2) invalid character that reaches the database layer, as demonstrated by a crafted character in a comment.

Patch / fix

  • wordpress Debian 14, Debian 13, Debian 12 4.2+dfsg-1

debian advisories DEBIAN-CVE-2015-3438

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3438 updated cvss 4.3

wordpress: several vulnerabilities fixed in Wordpress 4.1.2

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.39% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • cedricvb.be https://cedricvb.be/post/wordpress-stored-xss-vulnerability-4-1-2/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel 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.