Security readout for executives and security teams
Plain-English summary
This CVE describes a cross-site scripting flaw in the Black-LetterHead WordPress theme before version 1.6. A remote attacker could inject script or HTML through PATH_INFO handling on index.php. Business risk depends on whether any public WordPress site still uses this old theme version.
Executive priority
Treat as a targeted legacy web exposure check, not a broad emergency. Prioritize any public WordPress estate with old custom or abandoned themes.
Technical view
The issue is an XSS vulnerability in Black-LetterHead for WordPress before 1.6, triggered through PATH_INFO supplied to index.php. The provided sources do not include CVSS, CWE mapping, affected CPEs, exploit evidence, or detailed vendor remediation beyond the version boundary.
Likely exposure
Exposure appears limited to WordPress installations using the Black-LetterHead theme before version 1.6. The source bundle does not identify broader products, plugins, forks, or platform-level impact.
Exploitation context
The CVE states remote attackers can inject arbitrary web script or HTML. The bundle does not show CISA KEV listing, active exploitation, public exploit confirmation, or attack prevalence data.
Researcher notes
Evidence is sparse. The CVE record provides the vulnerability class, affected theme/version boundary, and input vector, but not scoring, exploit status, patch notes, or detailed vulnerable code context.
Mitigation direction
- Inventory WordPress sites for the Black-LetterHead theme and installed version.
- Update Black-LetterHead to version 1.6 or later where still used.
- Remove or replace the theme if it is unsupported or unnecessary.
- Check the referenced advisory and vendor guidance before accepting residual risk.
Validation and detection
- Confirm no production site runs Black-LetterHead before version 1.6.
- Review WordPress theme inventories across public-facing and archived sites.
- Check web logs for unusual PATH_INFO requests targeting index.php.
- Validate with authorized scanning that the XSS finding is no longer reported.
Public sources used
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-2011-3865 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://sitewat.ch/en/Advisories/24CVE 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.