# CVE-2026-108625: JeecgBoot through 3.9.5 Missing Authorization via sysMessage Edit Endpoint

> Low-privileged users can modify arbitrary message push records in JeecgBoot due to missing ownership checks on the edit endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 10 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-f2px-hmhw-mj87

## What is CVE-2026-108625?

CVE-2026-108625 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JeecgBoot through 3.9.5 contains a missing authorization vulnerability that allows low-privileged authenticated users to modify message push records by calling PUT /sys/message/sysMessage/edit. Attackers can submit a request body naming any sys_sms record id to overwrite its title, content, receiver address and send status without ownership checks.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108625 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108625 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108625 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108625 exists.

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

## Sources

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

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