Structured ContentWordPress extension · Wpsc Plugin
CVE-2023-49820
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 · uneditedImproper 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.5.3.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Structured Content (JSON-LD) #wpsc WordPress plugin. The plugin fails to properly sanitize user-supplied or stored JSON-LD data before rendering it in web pages, allowing malicious JavaScript to be injected and executed when users view affected content.
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
<= 1.5.3CVSS 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.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'Structured Content (JSON-LD)' or 'WPSC Structured Content', and note the version number displayedAffected if The displayed version is 1.5.3 or lower
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the Structured Content plugin shows as 'Active'Affected if The plugin is active and version is <= 1.5.3
-
Identify JSON-LD content entriesCheck if the plugin has created any custom post types or database entries containing JSON-LD structured data; look in WordPress admin for any Structured Content menu items or custom post types managed by the pluginAffected if The plugin is active with stored JSON-LD content and version <= 1.5.3
-
Inspect page source for unescaped outputView the HTML source of a page where structured content is rendered (typically product pages, articles, or schema markup areas), and search for the JSON-LD script tags; check if content within script tags or rendered HTML contains raw user input without escapingAffected if The rendered JSON-LD data contains unescaped HTML or JavaScript characters that could represent injected scripts
You are affected if the Structured Content (JSON-LD) plugin is active at version 1.5.3 or lower and outputs any stored JSON-LD data without proper sanitization on your pages.
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 dataUpdate to a patched version of the plugin if available; otherwise, implement proper input sanitization and output encoding for all JSON-LD data before rendering, using WordPress sanitization functions such as esc_html() and wp_kses() to neutralize potentially malicious scripts.
Fix this in Structured Content
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-49820 — 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-2023-49820 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