Skip to main content
VulnerabilityPublished

CVE-2026-18631: jeequan jeepay · Authorization Bypass

Affects jeequan jeepaySource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 11:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
jeequanjeepayAffected
  • 3.2.0 – 3.2.9
10 affected builds
Fixed in–
Mavencom.jeequan/jeepaypkg:maven/com.jeequan/jeepayOther threatsAffected
  • 3.2.0 – 3.2.9
10 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:jeequan:jeepay:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a patch is released, consider restricting access to the affected components and applying compensating controls to limit exposure.

Description

CVE-2026-18631 is an authorization bypass vulnerability in jeequan jeepay affecting versions 3.2.0 through 3.2.9. It involves the WebSecurityConfig function in the SysLogController component, allowing remote attackers to bypass authorization controls. The vulnerability has a medium severity score of 5.3. No official patch or vendor response has been documented, and public exploit code is available.

References

Community reviews

Loading reviews…