CVE-2026-112868

Interactive Content – H5P <= 1.17.9 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-10-21 18:00
dcs

Strategic Overview

Status
Patched in 1.17.10
Affected Plugin
Interactive Content – H5P
Affected Version
<= 1.17.9
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-112868
View all Interactive Content – H5P vulnerabilities

At a glance

CVE-2026-112868 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Interactive Content WordPress plugin, affecting versions <= 1.17.9. 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.17.10; sites on affected versions should update now. Disclosed October 2026, reported by dcs.

Vulnerability Overview

The Interactive Content – H5P plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.17.9. 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 Interactive Content <= 1.17.9 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 Interactive Content the fix is 1.17.10: builds <= 1.17.9 are affected, anything from 1.17.10 onward is not.

Remediation

Update to version 1.17.10, 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: Interactive Content 1.17.10 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-112868https://www.wordfence.com/threat-intel/vulnerabilities/id/4ac4472c-ad23-4d05-ad3e-7acbe9a9735chttps://nvd.nist.gov/vuln/detail/CVE-2026-112868

Related records

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