CVE-2026-119033

Schema & Structured Data for WP & AMP < 1.70 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-11-11 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 1.70
Affected Plugin
Schema & Structured Data for WP & AMP
Affected Version
< 1.70
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-119033
View all Schema & Structured Data for WP & AMP vulnerabilities

At a glance

CVE-2026-119033 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Schema & Structured Data for WP & AMP WordPress plugin, affecting versions < 1.70. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.70; sites on affected versions should update now. Disclosed November 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The Schema & Structured Data for WP & AMP plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 1.70. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Schema & Structured Data for WP & AMP < 1.70 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Schema & Structured Data for WP & AMP the fix is 1.70: builds < 1.70 are affected, anything from 1.70 onward is not.

Remediation

Update to version 1.70, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Schema & Structured Data for WP & AMP 1.70 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-119033https://www.wordfence.com/threat-intel/vulnerabilities/id/207447bb-b9ce-4535-b6b9-8a54d06823abhttps://nvd.nist.gov/vuln/detail/CVE-2026-119033

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C