dbcve.org
Shipengine Shipping QuotesWordPress extension · Enituretechnology

CVE-2024-13531

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 1.0.8 or later.
See remediation →
84/100
Remediation priority · High
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
The ShipEngine Shipping Quotes plugin for WordPress is vulnerable to SQL Injection via the 'edit_id' parameter in all versions up to, and including, 1.0.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

SQL injection vulnerability in the ShipEngine Shipping Quotes WordPress plugin via the unauthenticated 'edit_id' parameter allows attackers to inject arbitrary SQL queries due to insufficient input sanitization and lack of prepared statements, enabling extraction of sensitive data from the database.

MitigationUpdate the ShipEngine Shipping Quotes plugin to a version higher than 1.0.7 which implements proper input sanitization and prepared SQL statements; if no patched version is available, disable the plugin.

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
Shipengine Shipping QuotesWordPress extension
Affected:< 1.0.8

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Check installed plugin version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, find 'ShipEngine Shipping Quotes' and read the version number displayed under the plugin name. Alternatively, check the main plugin file (shipengine-shipping-quotes.php in wp-content/plugins/) for the 'Version' header in the plugin comment block.
    Affected if The version displayed is lower than 1.0.8 (for example, 1.0.7, 1.0.6, etc.)
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that 'ShipEngine Shipping Quotes' shows as 'Active' (not 'Inactive' or 'Must-Use').
    Affected if The plugin is currently active and the version is below 1.0.8
  3. Identify exposed endpoints
    Check if the WordPress site has any public-facing pages or AJAX endpoints that may invoke the plugin with the 'edit_id' parameter. Review plugin files for code handling the 'edit_id' GET or POST parameter (search for 'edit_id' in plugin PHP files).
    Affected if The plugin handles the 'edit_id' parameter without prepared statements and the installed version is below 1.0.8
  4. Verify database interaction
    Review plugin code that processes the 'edit_id' parameter to confirm it interacts with the database. Look for SQL queries where this parameter is used directly in query strings rather than bound via $wpdb->prepare() or similar.
    Affected if Direct SQL query construction using 'edit_id' is present and the plugin version is below 1.0.8

You are affected if the ShipEngine Shipping Quotes plugin is installed and active at a version lower than 1.0.8.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.8 or later
Fixed in 1.0.8
Interim mitigation

Update the ShipEngine Shipping Quotes plugin to a version higher than 1.0.7 which implements proper input sanitization and prepared SQL statements; if no patched version is available, disable the plugin.

Recommended fix High confidence

1.0.8

  1. Create a complete backup of your WordPress site including database and files
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Find 'ShipEngine Shipping Quotes' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.0.8 of the plugin
  5. Verify the plugin version shows 1.0.8 after update
  6. Test that the shipping quotes functionality continues to work correctly
  7. Clear any caching plugins if present

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shipengine Shipping Quotes Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

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