dbcve.org
VideoWordPress extension · Gumlet

CVE-2024-13576

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 1.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Gumlet Video plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'gumlet' shortcode in all versions up to, and including, 1.0.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Gumlet Video WordPress plugin fails to sanitize and escape user-supplied attributes in its 'gumlet' shortcode, allowing authenticated attackers with contributor-level permissions or higher to inject malicious JavaScript that persists in page content and executes whenever users view the affected pages.

MitigationUpgrade the Gumlet Video plugin to a version beyond 1.0.3 that implements proper input sanitization and output escaping for shortcode attributes, or remove the plugin if no patched version is available.

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
VideoWordPress extension
Affected:< 1.0.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Gumlet Video plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Gumlet Video' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'gumlet-video'.
    Affected if The plugin is installed and active in WordPress.
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Gumlet Video, and note the version number displayed below the plugin name. Compare this version to the affected range: versions prior to 1.0.4 are vulnerable.
    Affected if The installed version is lower than 1.0.4.
  3. Identify pages or posts using the gumlet shortcode
    In WordPress admin, go to Posts or Pages and search for content containing '[gumlet' shortcode syntax. Alternatively, query the wp_posts table in the database for posts containing the string 'gumlet' in the post_content field.
    Affected if Any post, page, or custom post type contains the [gumlet] shortcode in its content.
  4. Review user roles with contributor-level access
    In WordPress admin, go to Users > All Users and review the roles assigned to each user. Identify any users with Contributor, Author, Editor, or Administrator roles who could potentially create or edit content containing the shortcode.
    Affected if There are users with Contributor-level permissions or higher who can create or edit content.

A user is affected if the Gumlet Video plugin version is below 1.0.4 AND the [gumlet] shortcode is present in any published content, allowing an authenticated contributor or higher to inject malicious scripts.

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.4 or later
Fixed in 1.0.4
Interim mitigation

Upgrade the Gumlet Video plugin to a version beyond 1.0.3 that implements proper input sanitization and output escaping for shortcode attributes, or remove the plugin if no patched version is available.

Recommended fix High confidence

1.0.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Gumlet Video plugin in the list
  4. Click 'Update Now' if an update is available, or manually upload version 1.0.4
  5. Verify the plugin version shows 1.0.4 after updating
  6. Review existing posts and pages using the gumlet shortcode for any suspicious injected scripts and remove them if found

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

Fix this in Video Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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