# CVE-2026-101301: WPCode 2.0.0 - 2.3.9 - Unauthenticated Snippet Suppression via Safe Mode Bypass

> Unauthenticated attackers can bypass WPCode's safe mode to disable site snippets for their own requests, potentially hiding malicious code or altering site behavior.

- **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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-m9m9-jghh-m488

## What is CVE-2026-101301?

CVE-2026-101301 is a medium-severity vulnerability in Unknown WPCode, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPCode WordPress plugin before 2.4.0 does not correctly verify that a request is genuinely for the login screen before entering its snippet safe mode, allowing unauthenticated visitors to disable all of the site's automatically inserted snippets for their own requests.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-101301?


## How do I fix CVE-2026-101301?

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

## Is CVE-2026-101301 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101301 and fix it if it is affected.

What it is: CVE-2026-101301 is a medium-severity vulnerability in Unknown WPCode, published on 14 Oct 2026. 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-2026-101301 in the wild and no public exploit code.

Affected product: Unknown WPCode. 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-2026-101301/ (Markdown: https://insights.sbomify.com/CVE-2026-101301/index.md)
```

## Sources

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

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