# CVE-2026-123044: ContentPen < 1.1.1 - Unauthenticated Stored XSS via API Key Disclosure

> Unauthenticated users can use the exposed ContentPen REST API key to create posts with JavaScript that runs for any visitor, including administrators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** Yes
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-v973-hgc6-wrfw

## What is CVE-2026-123044?

CVE-2026-123044 is a high-severity hardcoded credentials vulnerability in Unknown ContentPen, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ContentPen WordPress plugin before 1.1.1 discloses its REST API key to unauthenticated users, who can then use it to create posts containing unfiltered JavaScript, leading to Stored XSS that executes in the browser of any visitor, including administrators.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.


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

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

## Is CVE-2026-123044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123044 is a high-severity hardcoded credentials vulnerability in Unknown ContentPen, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-123044 in the wild and no public exploit code.
Exposure: Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

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

## Sources

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

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