# CVE-2026-18631: jeequan jeepay PreAuthorize SysLogController.java WebSecurityConfig authorization

> Remote attackers can bypass authorization checks in the SysLogController to access system logs without proper permissions.

- **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:** 3 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-v7r9-m72q-vvwx

## What is CVE-2026-18631?

CVE-2026-18631 is a medium-severity missing authorization vulnerability in jeequan jeepay, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in jeequan jeepay up to 3.2.9. This vulnerability affects the function WebSecurityConfig of the file jeepay-manager/src/main/java/com/jeequan/jeepay/mgr/ctrl/sysuser/SysLogController.java of the component PreAuthorize Handler. The manipulation leads to authorization bypass. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-18631 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18631 is a medium-severity missing authorization vulnerability in jeequan jeepay, published on 3 Aug 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-18631 exists.

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

## Sources

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

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