CVE-2025-24290
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 · uneditedMultiple Authenticated SQL Injection vulnerabilities found in UISP Application (Version 2.4.206 and earlier) could allow a malicious actor with low privileges to escalate privileges.
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 · high confidenceMultiple authenticated SQL injection vulnerabilities exist in UISP Application versions 2.4.206 and earlier. An attacker with low-privilege credentials can exploit these vulnerabilities to inject malicious SQL queries, potentially escalating privileges to administrator levels and gaining full system access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Identify installed UISP versionAccess the UISP administrative interface and navigate to System Settings or About section to view the current software version. Alternatively, check the UIISP release notes or the application dashboard for the version number.Affected if The installed version is 2.4.206 or earlier (any version up to and including 2.4.206).
-
Verify low-privilege user accounts existIn the UISP admin panel, review the user management or user accounts section to list all created users and their assigned privilege levels. Look for non-administrator or standard user accounts.Affected if Any low-privilege (non-administrator) user accounts are present in the system, as these credentials can be used to exploit the SQL injection.
-
Confirm network accessibility of UISP interfaceDetermine if the UISP web interface is exposed to untrusted networks by checking firewall rules, reverse proxy configurations, or network zoning. Verify whether the management port (typically 443 or 8080) is accessible from the internet or external networks.Affected if The UISP interface is reachable from untrusted networks or the internet without proper network segmentation.
-
Review authentication logs for anomalous SQL-like activityExamine UISP server logs, authentication logs, or web access logs for unusual query patterns, SQL error messages, or repeated failed authentication attempts that may indicate SQL injection probing.Affected if Log entries show SQL syntax errors, suspicious query fragments, or patterns consistent with SQL injection attempts targeting the application.
You are affected if your UISP installation runs version 2.4.206 or earlier AND has low-privilege user accounts configured, particularly if the interface is network-accessible.
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.
dbcve · scopedUpgrade UISP Application to a version beyond 2.4.206. If immediate patching is not possible, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts, and restrict low-privilege user permissions to minimum necessary functions.
Latest stable UISP release (version newer than 2.4.206)
- 1. Log in to the UISP application with administrative credentials
- 2. Navigate to the System or Settings section to check the current UISP version
- 3. Back up the UISP configuration before performing any upgrade
- 4. Download the latest UISP version from the official Ubiquiti Downloads page (ui.com/downloads)
- 5. Follow Ubiquiti's standard upgrade procedure for UISP (typically via SSH or the web interface)
- 6. After upgrade, verify the application is functioning correctly
- 7. Confirm the new version is greater than 2.4.206
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24290 — 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-2025-24290 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