dbcve.org
Advance Seat Reservation Management For WoocommerceWordPress extension · Smartcmsmarket

CVE-2024-13344

HIGH · 7.5 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to 3.4 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 Advance Seat Reservation Management for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'profileId' parameter in all versions up to, and including, 3.3 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

The Advance Seat Reservation Management for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'profileId' parameter in versions up to 3.3. The plugin fails to properly escape user-supplied input and lacks prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries and extract sensitive data from the database.

MitigationUpdate the plugin to version 3.4 or later. If no patch is available, remove the plugin or implement WAF rules to block SQL injection attempts on the profileId parameter until a fix is released.

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
Advance Seat Reservation Management For WoocommerceWordPress extension
Affected:< 3.4

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
    In WordPress admin, go to Plugins > Installed Plugins and find 'Advance Seat Reservation Management for WooCommerce' (or 'Smartcmsmarket Advance Seat Reservation Management For Woocommerce'). The version number is displayed below the plugin name.
    Affected if The version listed is 3.3 or lower (any version before 3.4 is affected)
  2. Identify plugin files via filesystem
    Access the WordPress plugins directory (wp-content/plugins/) and locate the folder for the seat reservation plugin. Check the main plugin file (usually named main.php, index.php, or similar) for the version comment/header.
    Affected if The version comment in the plugin header shows a version before 3.4
  3. Verify the vulnerable profileId parameter exists
    Search the plugin source code for occurrences of 'profileId' - this is the vulnerable parameter. Look for files handling this parameter in AJAX handlers or frontend submission code.
    Affected if The plugin code contains handling of 'profileId' parameter without proper escaping or prepared statements
  4. Check for SQL injection indicators in access logs
    Review web server access logs (Apache/Nginx) for requests to the plugin's endpoints that contain 'profileId' parameter with suspicious SQL characters (quotes, UNION, SELECT, etc.). Logs are typically in /var/log/apache2/ or /var/log/nginx/.
    Affected if Requests containing SQL injection payloads in the profileId parameter are found in logs

The environment is affected if the plugin version is 3.3 or lower AND the plugin is active, since the unauthenticated profileId parameter vulnerability requires no authentication to exploit.

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 3.4 or later
Fixed in 3.4
Interim mitigation

Update the plugin to version 3.4 or later. If no patch is available, remove the plugin or implement WAF rules to block SQL injection attempts on the profileId parameter until a fix is released.

Recommended fix High confidence

Version 3.4

  1. Update the Advance Seat Reservation Management for WooCommerce plugin to version 3.4 or later via the WordPress plugin repository or WordPress admin dashboard
  2. Verify the update was successfully applied by checking the plugin version number
  3. Confirm the 'profileId' parameter is now properly handled with prepared statements or sufficient escaping

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

Fix this in Advance Seat Reservation Management For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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