dbcve.org
Structured ContentWordPress extension · Wpsc Plugin

CVE-2024-24839

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 1.6.1 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gordon Böhme, Antonio Leutsch Structured Content (JSON-LD) #wpsc allows Stored XSS.This issue affects Structured Content (JSON-LD) #wpsc: from n/a through 1.6.1.

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 · moderate confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in the Structured Content (JSON-LD) component of the wpsc plugin. The vulnerability allows an attacker to inject malicious JavaScript code into JSON-LD structured content, which is then stored and executed when other users view the affected web pages. This is a classic CWE-79 stored XSS flaw resulting from improper input sanitization during web page generation.

MitigationUpdate the plugin to the latest version immediately. Until a patch is available, review and sanitize all JSON-LD structured content inputs on the server side and ensure proper output encoding when rendering the content to prevent script execution.

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
Structured ContentWordPress extension
Affected:<= 1.6.1

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. Confirm WPSC plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'WPSC Plugin' or 'WordPress Support Collective' and note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/wpsc/ or equivalent directory.
    Affected if The installed version is 1.6.1 or lower.
  2. Identify if Structured Content (JSON-LD) feature is active
    Look for plugin settings related to Structured Content, JSON-LD, or schema markup. Check the plugin configuration pages or settings panels for any enabled options that generate JSON-LD structured data for SEO or ticket support pages.
    Affected if The Structured Content/JSON-LD feature is enabled in the plugin settings.
  3. Inspect stored JSON-LD content in the database
    Query the WordPress database (wp_postmeta or similar tables used by the plugin) for entries containing '_wpscStructuredContent', '_json_ld', 'structured_data', or similar meta keys. Examine the stored values for any unsanitized script tags, event handlers (onclick, onerror, etc.), or suspicious JavaScript code.
    Affected if The database contains JSON-LD structured content entries with unsanitized HTML, script tags, or JavaScript event handlers.
  4. Review page source for rendered JSON-LD output
    Visit public-facing pages where WPSC structured content is displayed (e.g., support ticket pages, landing pages). Right-click and view page source. Search for '<script type="application/ld+json">' or similar JSON-LD script blocks. Inspect the content between these tags for malicious script injections.
    Affected if The rendered JSON-LD output in page source contains script tags, event handler attributes, or executable JavaScript that was not properly escaped.

A user is affected if the WPSC plugin version is 1.6.1 or lower AND the Structured Content (JSON-LD) feature is enabled with unsanitized content present in stored data or rendered output.

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.

From vendor data
Upgrade available Upgrade to a release after 1.6.1
Interim mitigation

Update the plugin to the latest version immediately. Until a patch is available, review and sanitize all JSON-LD structured content inputs on the server side and ensure proper output encoding when rendering the content to prevent script execution.

Fix this in Structured Content Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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