dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13676

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-19
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 Categorized Gallery Plugin plugin for WordPress is vulnerable to SQL Injection via the 'field' attribute of the 'image_gallery' shortcode in all versions up to, and including, 2.0 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 Contributor-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 Categorized Gallery Plugin for WordPress is vulnerable to SQL Injection in the 'image_gallery' shortcode's 'field' attribute. The plugin fails to properly escape user-supplied input and does not use prepared statements, allowing authenticated users with Contributor-level access or higher to inject malicious SQL queries and potentially extract sensitive data from the database.

MitigationUpdate the plugin to version 2.0 or later where the vulnerability is patched. Review user access logs and database for signs of compromise, as the SQL injection could have been exploited prior to patching.

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. Identify plugin installation and version
    Navigate to WordPress admin dashboard > Plugins. Locate 'Categorized Gallery Plugin' and note the installed version number. Compare this version against the vulnerable range (versions prior to 2.0).
    Affected if The installed version is below 2.0 (e.g., 1.x, 0.x)
  2. Verify user roles with Contributor or higher access
    Go to WordPress admin > Users. Review the list of users and their assigned roles. Identify any accounts with Contributor, Author, Editor, or Administrator roles.
    Affected if There exists at least one user account with Contributor-level access or higher, enabling them to use the vulnerable shortcode
  3. Search for usage of the image_gallery shortcode
    In the WordPress admin, check Pages, Posts, or custom post types for content containing '[image_gallery' shortcode. Alternatively, search the database wp_posts table for 'image_gallery' string in post_content field.
    Affected if The shortcode [image_gallery field=...] is actively used on the site
  4. Inspect shortcode attribute usage
    Review any found image_gallery shortcode implementations and verify if the 'field' attribute is being used (e.g., [image_gallery field="something"]).
    Affected if The 'field' attribute is present in any shortcode usage, as this is the injection point
  5. Review access logs for suspicious SQL patterns
    Check web server access logs and WordPress debug logs for requests containing SQL injection patterns within the field parameter (e.g., UNION SELECT, information_schema, sleep(), hex() in URL parameters).
    Affected if Unusual SQL syntax appears in HTTP requests to pages containing the shortcode

A user is affected if the Categorized Gallery Plugin version is below 2.0 AND there exists at least one user with Contributor-level access who can utilize the image_gallery shortcode with the field attribute.

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 plugin to version 2.0 or later where the vulnerability is patched. Review user access logs and database for signs of compromise, as the SQL injection could have been exploited prior to patching.

Recommended fix Moderate confidence

Latest version > 2.0 (check WordPress plugin repository for the most recent release)

  1. Check the current version of the Categorized Gallery Plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. If the installed version is 2.0 or lower, update the plugin to the latest available version
  4. After updating, verify the plugin functions correctly on your site
  5. Consider testing the update in a staging environment first if possible

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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