Skip to main content

Schema Structured Data CVE-2026-82125

| EUVDEUVD-2026-80188 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-09-16 WPScan GHSA-44gp-9hmx-cr3c
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running plugin <1.66
  2. Exploit
    Send unauthenticated request for comment content
  3. Execution
    Plugin skips ownership/moderation check
  4. Impact
    Read pending/spam comment content

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of the Schema & Structured Data for WP & AMP WordPress plugin (versions 1.46 up to but not including 1.66). Exploitation only requires that the site run a vulnerable plugin version and that comments awaiting moderation or marked as spam exist to be read; no authentication, user interaction, or non-default settings are needed. The practical limit on impact is the data itself: only comment text (pending or spam) is exposed - no credentials, post/write access, or administrative capability - so severity stays low (C:L only).

Impact

This is a genuine but low-severity information-disclosure flaw, correctly scored at CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) - network-reachable, no privileges, no user interaction, but confidentiality-only with limited impact (C:L, I:N, A:N). CWE-639 (IDOR / authorization bypass through user-controlled key) matches the root cause: the plugin returns comment content without verifying ownership or moderation status. Signals are consistent and non-alarming: EPSS is 0.18% (8th percentile), it is NOT on CISA KEV, and while a POC exists via WPScan, POC availability is a distinct signal from active exploitation. The realistic impact is bounded - an attacker learns the text of pending/spam comments (potential PII or private feedback), not credentials, admin access, or write capability. Priority: LOW-to-MODERATE for defenders; patch during normal maintenance rather than as an emergency, but the unauthenticated network vector plus public POC means it can be trivially automated against unpatched sites, so do not defer indefinitely.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted request to a vulnerable site's plugin endpoint referencing a comment identifier, and the plugin returns the comment's content without checking whether it is approved, spam, or owned by the requester. Because publicly available exploit code exists (WPScan) and no authentication or user interaction is required (PR:N/UI:N), the attacker can enumerate identifiers to harvest the text of comments still awaiting moderation or flagged as spam.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 17, 2026

Unauthenticated information disclosure in the Schema & Structured Data for WP & AMP WordPress plugin (versions 1.46 up to but not including 1.66) allows a remote attacker to read the body text of comments that are still pending moderation or have been flagged as spam. Exploitation requires no authentication, no user interaction, and no non-default configuration - only a vulnerable plugin version plus the existence of at least one unapproved comment on the target site - and publicly available exploit code exists, though there is no confirmed active exploitation (CISA KEV) and EPSS is low at 0.18% (8th percentile). Impact is confined to confidentiality of comment text: no credentials, write access, or administrative capability is exposed, which is consistent with the assessed CVSS 5.3 (C:L/I:N/A:N).

RemediationAI

Vendor-released patch: upgrade Schema & Structured Data for WP & AMP to version 1.66 or later - the plugin code as shipped "before 1.66" contains the faulty comment-status check, so 1.66 is the minimum fixed release and the update should be applied through the WordPress plugin dashboard or WP-CLI (wp plugin update schema-and-structured-data-for-wp). If immediate upgrade is not possible, the most effective compensating control is to eliminate the data at risk: approve, delete, or purge all pending-moderation and spam comments (in bulk via Comments > Pending/Spam), which removes the exposed content but also destroys any legitimate comments awaiting review - export them to a moderation queue first if needed. A second option is to disable the plugin's comment/schema-markup output for comments in the plugin settings until patching, at the cost of losing comment-related rich results; a WAF rule blocking unauthenticated requests to the plugin's comment-data endpoint is a weaker, bypass-prone third option that risks breaking legitimate structured-data rendering for cached or proxied pages. Confirm the applied version matches the 1.66 fix, and re-check the WPScan advisory (https://wpscan.com/vulnerability/1ed1a2a1-e23d-4c4c-a933-f55b3e14ad09/) or EUVD-2026-80188 for any updated version guidance before closing the finding.

Affected VersionsENISA

Schema & Structured Data for WP & AMP 1.46 <1.66

Affected Packages

euvd schema_structured_data_for_wp_amp fix: 1.66

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 flaw is CWE-639 (Authorization Bypass Through User-Controlled Key): the plugin's schema/structured-data generation path accepts a comment identifier from the request and returns that comment's content without validating that the requester owns the comment or is permitted to see it. In WordPress, comment visibility is governed by the comment_approved status field in the wp_comments table (approved, pending/'0', spam, trash), and code that renders comment data must filter on that status (or check current_user_can('moderate_comments')) before emitting content. The plugin assembles comment data into JSON-LD structured markup for rich-result consumption, and the failing check means pending and spam comments are serialized and returned to anonymous callers. The supplied CPE record (cpe:2.3:a:unknown:schema_&_structured_data_for_wp_&_amp:*:*:*:*:*:*:*:*) is a wildcard with an unrecorded vendor, so the authoritative affected range comes from EUVD (Schema & Structured Data for WP & AMP 1.46 < 1.66) and the WPScan advisory; the vulnerability is network-reachable (AV:N), requires no privileges (PR:N) and no user interaction (UI:N), and is scoped unchanged (S:U).

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

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Unauthenticated network request with no interaction returns unmoderated comment content, so PR:N/UI:N and confidentiality-only C:L with no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 17, 2026 - 13:22 NVD
5.3 (MEDIUM)
Patch available
Sep 16, 2026 - 07:01 EUVD
CVE Published
Sep 16, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 16, 2026 - 06:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Schema & Structured Data for WP & AMP WordPress plugin before 1.66 does not correctly verify the ownership or the moderation status of a comment before returning its content, allowing unauthenticated users to read the content of comments still awaiting moderation or marked as spam.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
popular WordPress schema/structured-data plugin (Magazine3), large install base
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy