LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9344: The link-log plugin before 2.1 for WordPress has SQL injection.

The link-log plugin before 2.1 for WordPress has SQL injection.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2015-9344 is a reported SQL injection vulnerability in the WordPress link-log plugin before version 2.1. SQL injection can allow attackers to interfere with database-backed site behavior. The provided sources do not state severity, exploitability, authentication requirements, or confirmed exploitation.

Executive priority

Prioritize quick inventory and remediation for internet-facing WordPress sites using link-log. Business urgency is uncertain because the public data lacks severity and exploit details, but affected plugin versions should not remain exposed without a documented exception.

Technical view

The CVE record states that the link-log WordPress plugin before 2.1 has SQL injection. The source bundle does not identify the vulnerable parameter, request path, privilege requirement, CVSS score, CWE, or confirmed fixed changelog details beyond the affected pre-2.1 range.

Likely exposure

Exposure is limited to WordPress sites that installed the link-log plugin and are running a version before 2.1. The bundle does not provide CPEs, vendor metadata, or install prevalence, so asset inventory is required.

Exploitation context

The source bundle and KEV flag do not show active exploitation. Because the vulnerability class is SQL injection in a WordPress plugin, internet-facing sites using the affected plugin should still treat it as potentially material until version and exposure are confirmed.

Researcher notes

Evidence is sparse. The CVE description only states SQL injection in link-log before 2.1, with no technical root cause, endpoint, authentication context, payload details, or CVSS. Avoid assumptions beyond verifying installed plugin versions and consulting vendor sources.

Mitigation direction

  • Inventory WordPress sites for the link-log plugin and its installed version.
  • If link-log is before 2.1, update to a non-affected version if available.
  • If no supported update is available, disable or remove the plugin.
  • Check the WordPress plugin developer page for current vendor guidance.
  • Review change control for any business dependency before removal.

Validation and detection

  • Confirm whether each WordPress instance has the link-log plugin installed.
  • Record the exact installed plugin version for each affected site.
  • Verify whether any instance is running a version before 2.1.
  • Review application logs for unexplained SQL errors or suspicious requests.
  • Document remediation status and any remaining exception owners.
Prepared
Confidence
medium
Sources
3

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-9344 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
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
2Source links

CVSS and timeline data

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

Source materials

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.