Link LogWordPress extension · Perafox
CVE-2015-9344
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe link-log plugin before 2.1 for WordPress has SQL injection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe link-log plugin before version 2.1 for WordPress contains a SQL injection vulnerability. This allows remote attackers to manipulate database queries by injecting malicious SQL code through unsanitized input parameters, potentially enabling data exfiltration, privilege escalation, or complete site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Link LogWordPress extension
< 2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify link-log plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and search for 'Link Log' or 'Perafox Link Log'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'link-log' or similar.Affected if The Link Log plugin files exist in the WordPress plugins directory
-
Check if the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify whether the Link Log plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is activated and running on the site
-
Identify the installed version numberIn WordPress admin, go to Plugins > Installed Plugins. Locate the Link Log plugin entry and read the version number displayed beneath the plugin name. Compare this to version 2.1.Affected if The installed version is below 2.1, or the version cannot be verified but the plugin is present and active
The environment is affected if the Perafox Link Log plugin is installed, active, and its version is below 2.1, as this allows the SQL injection vulnerability to be exploited through unsanitized input parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.1
Update the link-log plugin to version 2.1 or later to obtain the security patch. If immediate updating is not feasible, disable or remove the plugin until the update can be applied.
Link Log version 2.1
- Backup your WordPress database and files before making any changes
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Link Log plugin in the list
- If an update is available, click 'Update Now' to update to version 2.1
- Alternatively, manually upload version 2.1 of the Link Log plugin by downloading it from wordpress.org
- Verify the plugin is running version 2.1 by checking the Plugins page
- Test that your site functionality remains intact after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Link Log
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data