Skip to main content
VulnerabilityPublished Updated

CVE-2024-48223: Funadmin v5.0.2 has a SQL injection

Affects funadminSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfunadmin/funadminpkg:github/funadmin/funadminOther threatsAffected
  • =5.0.2
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. Immediate mitigation involves applying any available patches or updates from Funadmin developers once released.
  2. If patches are not yet available, implement Web Application Firewall (WAF) rules to detect and block SQL injection payloads targeting the /curd/table/fieldlist endpoint.
  3. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters passed to SQL queries in the affected endpoint.
  4. Employ parameterized queries or prepared statements to prevent injection attacks at the code level.
  5. Restrict database user permissions to the minimum necessary, limiting the potential damage from a successful injection.
  6. Monitor logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint.
  7. Consider temporarily disabling or restricting access to the vulnerable endpoint if feasible until a patch is applied.
  8. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in the future.

Description

Funadmin v5.0.2 has a SQL injection vulnerability in /curd/table/fieldlist.

References

Community reviews

Loading reviews…