# CVE-2025-68505: WordPress H5P plugin <= 1.16.1 - Broken Access Control vulnerability

> Attackers can bypass access controls in the H5P WordPress plugin to perform unauthorized actions due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-938x-vjmp-c2cw

## What is CVE-2025-68505?

CVE-2025-68505 is a medium-severity missing authorization vulnerability in icc0rz H5P, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in icc0rz H5P h5p allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects H5P: from n/a through <= 1.16.1.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-68505?


## How do I fix CVE-2025-68505?

No fix has been published for CVE-2025-68505 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-68505 being exploited?

There is no known exploitation of CVE-2025-68505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68505 and fix it if it is affected.

What it is: CVE-2025-68505 is a medium-severity missing authorization vulnerability in icc0rz H5P, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68505 in the wild and no public exploit code.

Affected product: icc0rz H5P. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68505/ (Markdown: https://insights.sbomify.com/CVE-2025-68505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68505
- OSV: https://osv.dev/vulnerability/CVE-2025-68505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68505/
Summaries are generated and may contain mistakes; the official description above is the record.