dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-54353

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in wpgear Hack-Info hack-info allows Stored XSS.This issue affects Hack-Info: from n/a through <= 3.17.

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 · moderate confidence

A Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Hack-Info' (versions through 3.17) allows attackers to craft malicious requests that result in Stored XSS. The plugin lacks proper CSRF token validation, enabling authenticated or tricking administrators into submitting crafted forms that inject malicious scripts into the application.

MitigationImplement anti-CSRF tokens and validation on all state-changing operations in the plugin, particularly form submissions. Update to a patched version if available from the vendor.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify Hack-Info plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Hack-Info', or check the plugin file /wp-content/plugins/hack-info/hack-info.php for the 'Version' header comment. Compare this version number to the affected range (through 3.17).
    Affected if The plugin is installed and the version is 3.17 or lower.
  2. Verify CSRF protection on plugin forms
    Inspect the plugin PHP files (typically in /wp-content/plugins/hack-info/) for form handling code. Look for the presence of wp_nonce_field(), wp_verify_nonce(), or similar nonce verification functions in any form processing logic.
    Affected if Form handling code lacks nonce/token validation, meaning no CSRF protection exists.
  3. Inspect admin dashboard for injected scripts
    Navigate to the Hack-Info plugin settings page in WordPress admin. View the page source or inspect form fields, stored messages, or displayed content for any unexpected <script> tags, javascript: URIs, or event handlers (onerror, onload, etc.).
    Affected if Malicious script tags or XSS payloads are present in plugin-stored data.
  4. Check database for stored XSS payloads
    Query the WordPress options table (typically wp_options) for plugin-related entries. Look for unusual HTML or JavaScript code in option_name or option_value fields related to the Hack-Info plugin: SELECT * FROM wp_options WHERE option_name LIKE '%hack%' OR option_name LIKE '%hackinfo%'.
    Affected if Database contains suspicious encoded or plaintext XSS payloads in plugin configuration fields.

A user is affected if the Hack-Info plugin is installed at version 3.17 or lower and the plugin's form submissions lack CSRF token validation, allowing stored XSS injection.

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

Implement anti-CSRF tokens and validation on all state-changing operations in the plugin, particularly form submissions. Update to a patched version if available from the vendor.

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-2024-54353 — 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-2024-54353 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