Wp BibtexWordPress extension · Infinitescript
CVE-2024-13578
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 · uneditedThe WP-BibTeX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'WpBibTeX' shortcode in all versions up to, and including, 3.0.1 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 confidenceThe WP-BibTeX WordPress plugin (versions up to 3.0.1) contains a stored XSS vulnerability in its 'WpBibTeX' shortcode due to insufficient input sanitization and output escaping on user-supplied attributes, allowing authenticated attackers with contributor-level access to inject arbitrary JavaScript that executes when users view affected pages.
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
Wp BibtexWordPress extension
<= 3.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WP-BibTeX plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP-BibTeX' by Infinitescript, or check the plugin files in /wp-content/plugins/ for a folder named 'wp-bibtex' or similarAffected if The plugin is present on the WordPress site
-
Determine the installed plugin versionIn the WordPress plugin admin page, view the plugin details to see the version number, or check the main plugin PHP file for the 'Version' header in the plugin comment blockAffected if The version is 3.0.1 or lower (any version up to and including 3.0.1)
-
Check if the WpBibTeX shortcode is in useSearch the WordPress database (wp_posts table) or use a plugin to search post content for the string '[WpBibTeX' or '[wpbibtex'Affected if The shortcode appears in any published post, page, or custom post type content
-
Inspect shortcode attributes for unescaped outputExamine the plugin source code (the shortcode handler function) to verify if shortcode attributes are passed through sanitize_text_field, esc_attr, esc_html, or esc_js before outputAffected if Attributes are output without proper sanitization and escaping functions
A user is affected if the WP-BibTeX plugin version is 3.0.1 or lower AND the WpBibTeX shortcode is actively used on the site with user-supplied attributes that lack proper sanitization and escaping.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to the latest version of WP-BibTeX if a patch is available; otherwise remove or disable the plugin. Implement proper input sanitization (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_js) on all shortcode attributes before rendering.
Fix this in Wp Bibtex
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-13578 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13578 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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