CVE-2025-14184
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 · uneditedA vulnerability was determined in SGAI Space1 NAS N1211DS up to 1.0.915. Impacted is the function RENAME_FILE/OPERATE_FILE/NGNIX_UPLOAD of the file /cgi-bin/JSONAPI of the component gsaiagent. This manipulation causes command injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceCommand injection vulnerability in SGAI Space1 NAS N1211DS (up to v1.0.915) affecting the gsaiagent component. The /cgi-bin/JSONAPI endpoint exposes multiple functions (RENAME_FILE, OPERATE_FILE, NGINX_UPLOAD) that improperly sanitize user input, allowing unauthenticated remote attackers to inject and execute arbitrary operating system commands.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 the NAS device modelAccess the device admin interface or check system documentation to confirm the model is SGAI Space1 NAS N1211DSAffected if The device is an SGAI Space1 NAS N1211DS unit
-
Determine gsaiagent versionCheck the gsaiagent component version through the admin interface, system settings, or by querying the device API if accessible. Compare against v1.0.915Affected if gsaiagent version is v1.0.915 or earlier
-
Verify JSONAPI endpoint exposureProbe the /cgi-bin/JSONAPI endpoint with an HTTP request (e.g., curl http://TARGET/cgi-bin/JSONAPI) to confirm it is accessible and respondingAffected if The /cgi-bin/JSONAPI endpoint responds and is reachable over the network
-
Check network accessibility of CGI interfaceDetermine if the CGI interface (port 80/443 or the web server ports) is exposed to untrusted networks or the internet by reviewing firewall rules and network configurationAffected if The CGI interface is directly accessible from untrusted networks without authentication barriers
A user is affected if they operate an SGAI Space1 NAS N1211DS with gsaiagent version v1.0.915 or earlier and the /cgi-bin/JSONAPI endpoint 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.
From vendor dataSince the vendor did not respond, implement network segmentation to restrict access to the CGI interface, deploy firewall rules to limit exposure, and monitor for indicators of compromise until a vendor patch becomes available.
- Consultation6.0 h
- Implementation12.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14184 — 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-14184 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