# CVE-2026-9376: JPress UCenter Article Submission Endpoint doWriteSave improper authorization

> Remote attackers can manipulate article submission parameters to bypass authorization checks, potentially modifying data or escalating privileges in JPress.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-v6rp-6x79-xm3w

## What is CVE-2026-9376?

CVE-2026-9376 is a medium-severity missing authorization vulnerability in JPress, published on 24 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in JPress up to 1.0.3. The affected element is an unknown function of the file /ucenter/article/doWriteSave of the component UCenter Article Submission Endpoint. Executing a manipulation of the argument id/userId can lead to improper authorization. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-9376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9376 is a medium-severity missing authorization vulnerability in JPress, published on 24 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9376 in the wild and no public exploit code.

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

## Sources

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

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