CVE-2024-9430
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 Get Quote For Woocommerce – Request A Quote For Woocommerce plugin for WordPress is vulnerable to unauthorized access of Quote data due to a missing capability check on the ct_tepfw_wp_loaded function in all versions up to, and including, 1.0.0. This makes it possible for unauthenticated attackers to download Quote PDF and CSV documents.
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 confidenceThe Get Quote For Woocommerce plugin has a missing capability check on the ct_tepfw_wp_loaded function, allowing unauthenticated attackers to directly access and download quote PDF and CSV documents without any authentication or authorization.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Identify if the Get Quote For Woocommerce plugin is installedCheck the wp-content/plugins/ directory for a folder matching 'get-quote-for-woocommerce' or inspect the WordPress plugins admin page for this pluginAffected if The plugin folder exists in wp-content/plugins/
-
Check the installed plugin versionOpen the main plugin PHP file or readme.txt in the plugin directory and locate the Version headerAffected if The version is below or unknown, and the fixed version 1.0.0 or higher is not confirmed
-
Locate the vulnerable ct_tepfw_wp_loaded functionSearch within the plugin files for the string 'ct_tepfw_wp_loaded' using grep or a file search utilityAffected if The function exists and contains action or filter hooks without a capability check (such as current_user_can) before processing requests
-
Test unauthenticated access to quote documentsAttempt to access a known quote download URL pattern (such as /?ct_tepfw_download=pdf or /?ct_tepfw_download=csv) in a browser or via curl without being logged inAffected if The PDF or CSV file downloads successfully without any authentication prompt or 401/403 error
-
Verify access controls on quote download endpointsInspect the code handling the download request, looking for permission verification logic before file deliveryAffected if No current_user_can or similar authorization check is found before serving the file content
If the plugin is installed and its version is below 1.0.0 or unverified, and unauthenticated access to quote PDFs or CSVs is possible, the environment is affected by CVE-2024-9430.
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.
From vendor dataUpdate the plugin to a version beyond 1.0.0 that includes proper capability checks, or implement web server-level access restrictions as a temporary measure while investigating the fix.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9430 — 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-2024-9430 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