Unrestricted File Upload in Schema & Structured Data for WP & AMP (WordPress plugin) (CVE-2026-9067)
Summary
Vulnerability in Schema & Structured Data for WP & AMP (WordPress plugin) (CVE-2026-9067). Confidential information can be exposed externally.
Original description
The description as published by the source.
The Schema & Structured Data for WP & AMP WordPress plugin before 1.60 does not check user capabilities on its frontend AJAX file-upload handlers and does not validate the actual content of uploaded files against the endpoint's intended media type, allowing unauthenticated users to upload any file type accepted by WordPress's media library through endpoints that should only accept images or videos.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9067 has been found in Schema & Structured Data for WP & AMP (WordPress plugin).
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Schema & Structured Data for WP & AMP (WordPress plugin) CVE-2026-9067" on the vendor's site.
CVE-2026-9067 (Schema & Structured Data for WP & AMP (WordPress plugin)) — CWE-434 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-434) exists in Schema & Structured Data for WP & AMP (WordPress plugin).
Check the vendor advisory for the affected versions of Schema & Structured Data for WP & AMP (WordPress plugin).
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Schema & Structured Data for WP & AMP (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web contact@wpscan.com
- web nvd.nist.gov
- web wpscan.com
- web github.com