Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLoad public page with reviews shortcode
-
DeliveryHarvest exposed nonce from HTML
-
ExploitSubmit review with XSS in saswp_review_text
-
ExecutionPayload stored unsanitized in site
-
PersistVictim/admin views injected page
-
ImpactScript executes in victim browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a page on the target site render the [saswp-reviews-form] shortcode from the Schema & Structured Data for WP & AMP plugin, since that shortcode both exposes the submission form and publicly prints the nonce used as the sole authorization gate. Given that precondition, no authentication, privileges, or user interaction are needed by the attacker to inject the payload via the 'saswp_review_text' parameter (CVSS PR:N/UI:N). The main limiting factor is deployment-specific: sites that do not use the reviews form/shortcode, or that have the reviews module disabled, do not expose the vulnerable submission path. Execution of the stored payload occurs passively when any user subsequently views the injected page. |
| Impact | This is a genuine, exploitable issue rather than a paper-tiger high-CVSS finding, but it sits in the mid-tier of urgency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C) describes a network-reachable, low-complexity, unauthenticated flaw with a changed scope, and the description corroborates each metric: the only authorization gate (a nonce) is printed directly in the public [saswp-reviews-form] shortcode HTML, so any anonymous visitor can harvest it, which legitimately justifies PR:N. The scope change (S:C) and the fact that injected script executes in the browser of any later visitor explain why impact is rated C:L/I:L despite stored XSS normally needing a victim to load the page. Countervailing signals temper the priority: no EPSS probability was supplied, there is no CISA KEV listing, and no public proof-of-concept is referenced - only a Wordfence vulnerability record and WordPress.org trac source links. There is no evidence of active exploitation; treat this as a patch-soon web application flaw, not an emergency. One point to verify with the vendor: the description states 'all versions up to, and including, 1.67,' yet every source/trac reference points at tag 1.66, so the exact first-fixed version should be confirmed against the Magazine3 changelog. |
| Exploit ScenarioDerived | An anonymous attacker loads a page containing the [saswp-reviews-form] shortcode, reads the authorization nonce printed in that page's HTML, and submits a review whose 'saswp_review_text' field contains a malicious script payload. Because the input is stored without sufficient sanitization and rendered without output escaping, the script later executes in the browser of every visitor (including logged-in administrators) who views the affected page, enabling session/cookie theft or admin-context actions. No public exploit code is referenced, but the attack is simple enough to reproduce from the description alone. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Stored cross-site scripting in the Schema & Structured Data for WP & AMP plugin (versions up to 1.67) allows unauthenticated attackers to inject arbitrary JavaScript via the 'saswp_review_text' parameter, because the nonce used as the sole authorization check is publicly exposed in the [saswp-reviews-form] shortcode. Exploitation requires the shortcode to be present, making it a genuine but deployment-specific issue that sits in the mid-tier of urgency. No public exploit code or active exploitation has been identified at time of analysis.
RemediationAI
No vendor-released fixed version is explicitly identified in the available data; an upstream changeset (revision 3740790) is referenced at https://plugins.trac.wordpress.org/changeset?reponame=&old=3740790%40schema-and-structured-data-for-wp&new=3740790%40schema-and-structured-data-for-wp, which may contain the fix. Patch status: Upstream fix available (changeset/commit); released patched version not independently confirmed. Until a patched release is available, the most effective mitigation is to disable the reviews module or remove the [saswp-reviews-form] shortcode from all pages, which eliminates the vulnerable attack vector. Note that this will disable the reviews functionality for legitimate users. As a compensating control, a web application firewall can be configured to block malicious payloads in the 'saswp_review_text' parameter, but this is less reliable than removing the shortcode. Monitor the plugin's page and the Wordfence advisory for updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic stored cross-site scripting (CWE-79) in a WordPress plugin, arising from insufficient input sanitization of the 'saswp_review_text' parameter and missing output escaping when the review is rendered. The plugin's reviews module uses a nonce as the sole authorization gate for the submission form, but the nonce is printed in the HTML of the [saswp-reviews-form] shortcode, making it visible to any anonymous visitor and thus defeating its purpose. An attacker can therefore submit a review containing malicious JavaScript, which is stored and later executed in the browser of any user viewing the affected page. The affected CPE is cpe:2.3:a:magazine3:schema_&_structured_data_for_wp_&_amp:*:*:*:*:*:*:*:*, confirming the product is magazine3's Schema & Structured Data for WP & AMP.
Know when Schema Structured Data For Wp Amp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Publicly exposed nonce leaves no real auth barrier so PR:N and AC:L; network-delivered stored XSS executing in other users' browsers justifies S:C with C:L/I:L and A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'saswp_review_text' parameter in all versions up to, and including, 1.67 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nonce that serves as the only authorization gate is publicly printed in the [saswp-reviews-form] shortcode HTML, making it obtainable by any anonymous visitor and rendering it ineffective as an access control boundary.
Executive ViewAI
A stored cross-site scripting vulnerability in the Schema & Structured Data for WP & AMP plugin (versions up to and including 1.67) affects any WordPress site that publishes the [saswp-reviews-form] shortcode, allowing attacker-supplied JavaScript to be stored and later executed in the browsers of site visitors and administrators. Because the plugin's sole authorization check relies on a nonce that is publicly exposed on the page itself, the injection path is reachable without stolen credentials or privileged access. Leadership should care because successful exploitation can enable session hijacking, administrator account takeover, and reputational damage on public-facing sites, although exposure is limited to the subset of sites that actually render the affected shortcode.
No vendor-released patch identified at time of analysis. Interim mitigations: remove or disable the [saswp-reviews-form] shortcode and temporarily deactivate the plugin on affected sites, deploy WAF/virtual-patch rules blocking script content in the saswp_review_text parameter, restrict or moderate review submissions, and review stored review text for injected JavaScript.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Unauthenticated arbitrary file upload in the Schema & Structured Data for WP & AMP WordPress plugin before version 1.60
Unauthenticated visitors can read the body content of WordPress posts that authors marked as password protected when the
Unauthenticated information disclosure in the Schema & Structured Data for WP & AMP WordPress plugin (versions 1.46 up t
PHP object injection in the Schema & Structured Data for WP & AMP plugin (all versions up to and including 1.66) lets an
Information disclosure in the Schema & Structured Data for WP & AMP WordPress plugin (versions 1.63 through 1.65) allows
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Magazine3 Schema &
The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plug
The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the cust
The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to unauthorized modification of data due to
EUVD-2026-102657
GHSA-cmj8-gm9j-p86q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB