# CVE-2026-108803: y_project RuoYi Disable API add changeStatus session expiration

> Attackers can bypass session expiration controls in the RuoYi admin framework via the changeStatus function, potentially maintaining unauthorized access.

- **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:X`)
- **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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-g882-pgw7-c79v

## What is CVE-2026-108803?

CVE-2026-108803 is a medium-severity vulnerability in y_project RuoYi, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in y_project RuoYi up to 4.8.3. This impacts the function changeStatus of the file /system/config/add of the component Disable API. The manipulation leads to session expiration. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-108803 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108803 is a medium-severity vulnerability in y_project RuoYi, published on 12 Oct 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-108803 in the wild and no public exploit code.

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

## Sources

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

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