CVE-2024-57773: JFinalOA · n/a
Affects JFinalOASource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2025.01.01 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.01.01
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 2025
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
Upgrade r1bbit/JFinalOA to 2025.01.01.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubr1bbit/JFinalOApkg:github/r1bbit/JFinalOAOther 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
1. Upgrade JFinalOA to version 2025.01.01 or later once the patch is officially released to address the vulnerability. 2. If you cannot patch yet, implement strict input validation and output encoding on the openSelectManyUserPage?orgid interface to neutralize malicious payloads. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. 4. Limit the number of users with high privileges and enforce the principle of least privilege to reduce the attack surface. 5. Educate privileged users about the risks of interacting with untrusted links or payloads to mitigate social engineering vectors. 6. Monitor web application logs and user activity for signs of suspicious behavior or attempted exploitation. 7. Employ web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting the affected interface. 8. Conduct regular security assessments and penetration testing focused on input validation and XSS vulnerabilities in JFinalOA deployments.
Description
A cross-site scripting (XSS) vulnerability in the openSelectManyUserPage?orgid interface of JFinalOA before v2025.01.01 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.