Skip to main content
VulnerabilityPublished

CVE-2026-90520: jaychouchannel Tourism-Management-System · CWE-266

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-90520· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 18 Nov 2026, 20:25 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 30% 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 13 Sep 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
jaychouchannelTourism-Management-SystemAffected
  • =84d8ec384f669df3985293dab293bb7b477efa64
Fixed in–

AI-suggested

Apply the patch identified by commit d984d172dceca907f8b447efbdb06dc233f7938d to remediate the improper authorization vulnerability. Since the product uses a rolling release model, ensure the latest updates incorporating this patch are deployed. No other mitigations are specified.

Description

A vulnerability in the AuthorizationInterceptor component of jaychouchannel Tourism-Management-System allows improper authorization due to a flaw in AuthorizationInterceptor.java. The issue can be exploited remotely and has public exploit code disclosed. The product uses a rolling release model, so no specific affected or fixed versions are identified. A patch identified by commit d984d172dceca907f8b447efbdb06dc233f7938d is recommended to remediate the issue.

References

Community reviews

Loading reviews…