Security readout for executives and security teams
Plain-English summary
CVE-2015-9345 affects the WordPress link-log plugin before version 2.0. The issue is HTTP response splitting, a web response handling flaw that can let responses be manipulated in unsafe ways. The source bundle provides no CVSS score, no confirmed exploitation, and limited product metadata.
Executive priority
Treat this as a targeted legacy WordPress plugin cleanup item, not an emergency based on current evidence. Prioritize internet-facing WordPress sites and environments where plugin inventory is weak.
Technical view
The public record states that link-log before 2.0 for WordPress has HTTP Response Splitting. That class can affect header and response boundary handling, with impact depending on reachable plugin code paths. No CVSS vector, CWE mapping, exploit status, or detailed vulnerable endpoint is provided in the bundle.
Likely exposure
Exposure is likely limited to WordPress sites with the link-log plugin installed below version 2.0. The affected metadata lists vendor, product, versions, and CPEs as n/a, so CPE-only asset matching may miss this issue.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. The available public description is sparse, so attacker prerequisites, reachable paths, and real-world abuse are not established by the supplied evidence.
Researcher notes
The record is minimal: no CVSS, no CWE, no CPEs, and no endpoint details. Validation should focus on plugin presence and version. Avoid assuming broader WordPress exposure beyond link-log before 2.0.
Mitigation direction
- Inventory WordPress sites for the link-log plugin and installed version.
- Upgrade link-log installations below 2.0 where a trusted vendor package is available.
- Remove the plugin if it is unused or cannot be safely updated.
- Check WordPress plugin guidance for current maintenance and replacement options.
Validation and detection
- Confirm whether link-log is installed on each WordPress instance.
- Verify installed plugin versions are 2.0 or later.
- Review web server and application logs for unusual response header behavior.
- Document sites where plugin status cannot be confirmed.
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-2015-9345 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://wordpress.org/plugins/link-log/#developersCVE 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.