Schema \& Structured Data For Wp \& AmpWordPress extension · Magazine3
CVE-2024-22146
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 Magazine3 Schema & Structured Data for WP & AMP allows Stored XSS.This issue affects Schema & Structured Data for WP & AMP: from n/a through 1.25.
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 confidenceThis is a Stored XSS vulnerability in the Magazine3 Schema & Structured Data for WP & AMP WordPress plugin. The plugin fails to properly sanitize user-supplied input, allowing malicious JavaScript to be stored in the database and executed when other users (typically administrators) view pages displaying the unsanitized 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
Schema \& Structured Data For Wp \& AmpWordPress extension
<= 1.25CVSS 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.
-
Verify Magazine3 plugin is installedGo to WordPress admin dashboard > Plugins > Installed Plugins, look for 'Magazine3 Schema & Structured Data For Wp & Amp' in the listAffected if Plugin is present in the WordPress installation
-
Check installed plugin versionIn the Plugins list, click on the plugin to view details, or check the plugin files in wp-content/plugins/mas-schema/ for a version file or readme.txtAffected if Version is 1.25 or lower (e.g., 1.25, 1.24, 1.23, etc.)
-
Identify active schema features in useNavigate to the plugin settings (usually under Mas Schema or Schema in the admin sidebar) and review which schema types are enabled and contain user-defined content, such as Article, Post, or custom schema typesAffected if The plugin is actively collecting and storing schema data through its input fields
-
Inspect stored schema data in databaseQuery the WordPress database (wp_postmeta table, looking for meta_keys like _mas_schema_* or similar prefixes used by the plugin) or use a plugin like WP Data Access to view stored schema values; look for unsanitized HTML or script tags within stored contentAffected if Stored schema entries contain raw HTML, script tags, or JavaScript event handlers that were not escaped
If the plugin version is 1.25 or lower and the plugin is actively storing schema data, the environment is likely vulnerable to stored XSS.
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 the plugin to the latest version (after 1.25) which should include proper input sanitization and output encoding to prevent XSS attacks.
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
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 locallyCheck whether your project pulls in CVE-2024-22146 — 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-22146 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