dbcve.org
Schema \& Structured Data For Wp \& AmpWordPress extension · Magazine3

CVE-2024-5582

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-17
Fix available
A fix is available. Upgrade to 1.34.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
The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'url' attribute within the Q&A Block widget in all versions up to, and including, 1.33 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 Schema & Structured Data for WP & AMP WordPress plugin versions up to 1.33 contain a stored XSS vulnerability in the Q&A Block widget's 'url' attribute. Authenticated attackers with contributor-level permissions can inject arbitrary JavaScript through unsanitized input that is not properly escaped upon output.

MitigationUpdate the plugin to version 1.34 or later which includes proper input sanitization and output escaping for the affected attribute.

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
Schema \& Structured Data For Wp \& AmpWordPress extension
Affected:< 1.34.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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Schema & Structured Data for WP & AMP' by Magazine3. Note the installed version displayed.
    Affected if Plugin is installed with version 1.33 or earlier (any version below 1.34.1)
  2. Confirm installed version number
    Locate the version number in the plugin description or plugin file header (typically in schema-wp-amp.php main file). Compare against affected range: versions below 1.34.1 are vulnerable.
    Affected if Version is 1.33 or lower, or any version below 1.34.1
  3. Identify Q&A Block usage
    Check WordPress pages, posts, or widgets where the Q&A Block (part of the Schema & Structured Data plugin) has been added. Inspect the block settings for a 'url' attribute field.
    Affected if Q&A Block with a url attribute is present in any published content
  4. Inspect url attribute for suspicious content
    Examine the Q&A Block url field values in the database (wp_posts meta table) or via block editor. Look for JavaScript: URLs, event handlers (onclick, onerror), or HTML script tags.
    Affected if The url field contains unescaped HTML or JavaScript code such as <script>, javascript:, or event handler attributes

Environment is affected if the Magazine3 Schema & Structured Data plugin is installed with any version below 1.34.1 and the Q&A Block widget with a url attribute is in use.

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.34.1 or later
Fixed in 1.34.1
Interim mitigation

Update the plugin to version 1.34 or later which includes proper input sanitization and output escaping for the affected attribute.

Recommended fix High confidence

Schema & Structured Data for WP & AMP version 1.34.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Schema & Structured Data for WP & AMP' in the plugin list
  4. Check if the current version is below 1.34.1
  5. If update available, click 'Update Now' to upgrade to version 1.34.1
  6. Alternatively, go to Dashboard > Updates and select the plugin to update
  7. After updating, verify the plugin version shows 1.34.1 or higher

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

Fix this in Schema \& Structured Data For Wp \& Amp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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