CVE-2024-48230: funadmin · SQL Injection
Affects funadminSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Oct 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfunadmin/funadminpkg:github/funadmin/funadminOther 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-48230, organizations should immediately assess their use of funadmin 5.0.2 and related versions. If possible, upgrade to a patched version once available from the vendor. In the absence of official patches, apply the following specific mitigations: 1) Implement strict input validation and sanitization on the parentField parameter to block malicious SQL payloads. 2) Employ parameterized queries or prepared statements in the affected code to prevent injection. 3) Restrict database user permissions to the minimum necessary, limiting the impact of potential injection. 4) Deploy Web Application Firewalls (WAFs) with rules targeting SQL Injection patterns, especially on the vulnerable endpoint. 5) Monitor application and database logs for suspicious queries or anomalies indicative of injection attempts. 6) Conduct thorough code reviews and penetration testing focused on SQL Injection vectors in the authentication backend. 7) Isolate the affected application components in network segments with limited access to critical systems. 8) Educate development and security teams about secure coding practices to prevent similar vulnerabilities. These targeted actions go beyond generic advice and address the specific nature of this vulnerability.
Description
funadmin 5.0.2 is vulnerable to SQL Injection via the parentField parameter in the index method of \backend\controller\auth\Auth.php.