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

CVE-2024-31105

HIGH · 7.1 CVSS v3.1 Published 2024-04-02
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 Adam Bowen Tax Rate Upload allows Reflected XSS.This issue affects Tax Rate Upload: from n/a through 2.4.5.

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 CSRF vulnerability in the Tax Rate Upload plugin enables reflected XSS attacks. An attacker can trick authenticated administrators into submitting a malicious request that reflects unsanitized input back to the user, executing arbitrary JavaScript in the victim's browser. The vulnerability affects versions through 2.4.5.

MitigationImplement anti-CSRF tokens on all state-changing forms and validate/sanitize all user inputs before reflecting them in responses to prevent XSS execution.

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. Locate Tax Rate Upload plugin
    Check your e-commerce or CMS platform's plugin directory for 'Tax Rate Upload' or 'Tax Rate' related extensions. Common locations: WordPress wp-content/plugins/, Magento app/code/, Shopify apps/, or WooCommerce extensions.
    Affected if The plugin is installed and listed in the platform's plugin/extension manager.
  2. Identify installed version
    Access the plugin's details panel in your platform's admin interface (typically under Plugins > Installed or Extensions > Management). Note the version number displayed. Alternatively, inspect the plugin's main file header for a 'Version:' comment.
    Affected if The displayed version is 2.4.5 or any lower version number (e.g., 2.4.0, 2.3.1, 1.x).
  3. Verify plugin is active
    Check the plugin status in your admin panel. Look for an 'Active', 'Enabled', or 'Installed' indicator next to the Tax Rate Upload plugin entry.
    Affected if The plugin shows as active or enabled on your system.
  4. Check for tax rate upload functionality
    Navigate to the plugin's settings or configuration page. Look for any form or interface labeled 'Tax Rate Upload', 'Import Tax Rates', or similar upload functionality.
    Affected if The upload form is present and accessible in the admin dashboard.

Your environment is affected if the Tax Rate Upload plugin is installed, active, and running version 2.4.5 or lower.

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 on all state-changing forms and validate/sanitize all user inputs before reflecting them in responses to prevent XSS execution.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31105 — 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-31105 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