Security readout for executives and security teams
CVE-2015-3429 is a cross-site scripting issue in the sample example.html file bundled with Genericons, including WordPress before 4.2.2. If exposed, an attacker could cause script to run in a visitor's browser through a malicious URL fragment. Business urgency is mainly for older WordPress sites, themes, plugins, or Linux packages still carrying that file. Exposure is most likely on legacy WordPress installations, themes, plugins, or packaged web roots that still publish Genericons example.html. Current, patched WordPress deployments should be lower risk, but copied assets can persist outside package managers. Treat as a legacy web hygiene issue with moderate priority. Prioritize internet-facing WordPress estates, especially abandoned microsites and copied theme assets, because the vulnerable file can remain exposed after partial upgrades. Mitigation focus: Upgrade WordPress to 4.2.2 or later where applicable.; Update Genericons to 3.3.1 or later.; Remove public copies of Genericons example.html from web roots..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2015-3429 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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://www.digitalocean.com/community/tutorials/how-to-protect-your-wordpress-site-from-the-genericons-example-html-xss-vulnerabilityCVE reference · x_refsource_MISC
- https://wpvulndb.com/vulnerabilities/7965CVE reference · x_refsource_MISC
- https://github.com/Automattic/Genericons/commit/798ac98579dd72dfdb11bdee3e7bebf01cffb1f7CVE reference · x_refsource_CONFIRM
- https://wordpress.org/news/2015/05/wordpress-4-2-2/CVE reference · x_refsource_CONFIRM
- https://www.netsparker.com/cve-2015-3429-dom-xss-vulnerability-in-twenty-fifteen-wordpress-theme/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.