dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13809

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Hero Slider - WordPress Slider Plugin plugin for WordPress is vulnerable to SQL Injection via several parameters in all versions up to, and including, 1.3.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 Hero Slider WordPress plugin versions up to 1.3.5 contain a SQL injection vulnerability due to insufficient escaping of user-supplied parameters combined with lack of prepared statements in SQL queries. Authenticated attackers with Subscriber-level access or higher can inject malicious SQL queries through vulnerable parameters to extract sensitive data from the database.

MitigationUpdate the Hero Slider plugin to a version beyond 1.3.5 when available, or disable the plugin until a patched version is released. If immediate patching is not possible, restrict subscriber-level user creation and audit existing user accounts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Hero Slider plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Hero Slider' in the list. Note the installed version displayed next to the plugin name.
    Affected if Plugin is installed and version is 1.3.5 or lower
  2. Confirm the exact version number
    Click on 'View details' or access the plugin files via FTP/cPanel at wp-content/plugins/hero-slider/ and read the main plugin file (usually hero-slider.php) to find the defined version constant.
    Affected if Version defined is 1.3.5 or any version below it
  3. Identify user accounts with Subscriber role
    In WordPress admin, go to Users > All Users and filter by 'Subscriber' role, or use wp-cli: wp user list --role=subscriber
    Affected if One or more Subscriber-level accounts exist in the system
  4. Check if plugin is actively used on the site
    Review pages using the Hero Slider shortcode or widget, or inspect the database wp_options table for hero_slider related active configurations.
    Affected if Plugin is active and serving slider content on the site

A user is affected if the Hero Slider plugin version is 1.3.5 or lower AND the site has at least one Subscriber-level user account AND the plugin is actively configured.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Hero Slider plugin to a version beyond 1.3.5 when available, or disable the plugin until a patched version is released. If immediate patching is not possible, restrict subscriber-level user creation and audit existing user accounts.

Recommended fix Moderate confidence

Latest version after 1.3.5 (check WordPress plugin repository for version 1.3.6 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Hero Slider - WordPress Slider Plugin'
  4. Check if an update is available and update to the latest version
  5. If no update is shown in WordPress, manually download the latest version from the WordPress plugin repository or the vendor's site and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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