dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31531

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in click5 History Log by click5 history-log-by-click5 allows SQL Injection.This issue affects History Log by click5: from n/a through <= 1.0.13.

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 confidence

A SQL injection vulnerability exists in the click5 History Log WordPress plugin (versions <= 1.0.13) due to improper neutralization of special elements in SQL commands. Attackers can inject malicious SQL queries through unsanitized input parameters, potentially allowing unauthorized database access, data exfiltration, or data modification.

MitigationUpgrade to the latest version of the History Log by click5 plugin (currently 1.0.14 or later). If no update is available, sanitize all user-supplied input before use in SQL queries and implement prepared statements/parameterized queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the History Log plugin directory
    Check your WordPress installation at wp-content/plugins/ for a directory named 'click5-history-log' or similar containing the History Log plugin files
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually click5-history-log.php) and locate the version string in the plugin header comment (e.g., 'Version: 1.0.x')
    Affected if The version string cannot be found or shows an unlisted version number
  3. Compare your version to the affected range
    Review the version found in step 2 and compare it against the affected versions (all versions <= 1.0.13)
    Affected if Your installed version is 1.0.13 or any earlier version (e.g., 1.0.12, 1.0.11, etc.)
  4. Confirm the plugin is active
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and verify whether the History Log by click5 plugin is currently activated
    Affected if The plugin is active and your version is <= 1.0.13

You are affected if the click5 History Log plugin is installed, active, and running version 1.0.13 or earlier.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of the History Log by click5 plugin (currently 1.0.14 or later). If no update is available, sanitize all user-supplied input before use in SQL queries and implement prepared statements/parameterized queries.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31531 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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