CVE-2015-3438: n/a vulnerability

CVE-2015-3438: Multiple cross-site scripting (XSS) vulnerabilities in WordPress before 4.1.2, when MySQL is used without s...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 05:47 UTC (UTC+00:00)

Security readout for executives and security teams

This vulnerability affected WordPress sites before 4.1.2 in a specific database configuration. Malicious content could be stored through user input such as comments and later run as script in a viewer's browser. The main business risk is account/session compromise or unauthorized actions by trusted users who view the content. Exposure is most likely on legacy WordPress installations older than 4.1.2 using MySQL without strict mode, especially where anonymous or low-trust users can submit comments or similar stored content. Prioritize remediation for internet-facing WordPress sites that accept public comments or user content. The issue is old and patched, but legacy systems remain plausible exposure points and stored XSS can affect administrators who view malicious content. Mitigation focus: Upgrade WordPress to 4.1.2 or a currently supported release.; Apply relevant distribution packages from Debian, Fedora, or your OS vendor.; Review vendor guidance before relying on MySQL strict mode as mitigation..

Prepared: Jun 13, 2026, 22:22 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2015-3438 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Aug 5, 2015, 01:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://wpvulndb.com/vulnerabilities/7929CVE reference · x_refsource_MISC
https://wordpress.org/news/2015/04/wordpress-4-1-2/CVE reference · x_refsource_CONFIRM
https://cedricvb.be/post/wordpress-stored-xss-vulnerability-4-1-2/CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.