CVE-2024-33338: jizhicms · n/a
Affects jizhicmsSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubcherry-toto/jizhicmspkg:github/cherry-toto/jizhicmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-33338, organizations should immediately implement input validation and output encoding on all user-supplied data, particularly in the article publication module. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Monitor web application logs for unusual or malformed requests targeting article publication endpoints. If possible, restrict access to the CMS backend by IP whitelisting or VPN to reduce exposure. Conduct thorough security testing, including automated and manual XSS detection, on all CMS inputs. Stay updated with vendor advisories for official patches and apply them promptly once available. Additionally, educate content managers and administrators about the risks of XSS and encourage the use of secure content creation practices. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting jizhicms.
Description
Cross Site Scripting vulnerability in jizhicms v.2.5.4 allows a remote attacker to obtain sensitive information via a crafted article publication request.