CVE-2024-48229
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedfunadmin 5.0.2 has a SQL injection vulnerability in the Curd one click command mode plugin.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA SQL injection vulnerability exists in the Curd one click command mode plugin of funadmin version 5.0.2, allowing an authenticated attacker to inject malicious SQL queries through plugin parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Funadmin versionLocate and inspect the Funadmin version file or admin interface version display to determine the installed version numberAffected if The installed version is exactly 5.0.2
-
Confirm Curd plugin is installedAccess the plugin management section of the Funadmin admin panel or inspect the plugins directory to verify the Curd plugin is present and enabledAffected if The Curd plugin is installed and active in the system
-
Check one click command mode statusNavigate to the Curd plugin settings or configuration area within the Funadmin admin panel to verify if the one click command mode feature is enabledAffected if The one click command mode feature is turned on in the Curd plugin configuration
-
Review access logs for SQL injection attemptsExamine Funadmin application logs, web server logs, or database audit logs for suspicious SQL syntax or unexpected queries originating from plugin parametersAffected if SQL injection patterns are found in logs with requests to Curd plugin endpoints
-
Inspect plugin parameter handlingReview the Curd plugin source code or configuration files to verify if user-supplied parameters are being used directly in SQL queries without proper sanitization or parameterized queriesAffected if Plugin parameters appear to be concatenated directly into SQL queries without prepared statements
A user is affected if running Funadmin version 5.0.2 with the Curd plugin installed and the one click command mode feature enabled, allowing authenticated SQL injection through plugin parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of funadmin if available, or implement proper input validation and parameterized queries in the Curd plugin to neutralize SQL injection vectors.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48229 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data