CVE-2025-1338
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 found in NUUO Camera up to 20250203. It has been declared as critical. This vulnerability affects the function print_file of the file /handle_config.php. The manipulation of the argument log leads to command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. 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 · moderate confidenceCommand injection vulnerability in NUUO Camera's /handle_config.php where the print_file function fails to sanitize the 'log' parameter, allowing remote attackers to inject and execute arbitrary OS commands. The vulnerability is exploitable without authentication and a public exploit exists.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 device as a NUUO CameraAccess the device web interface and look for NUUO branding, model number, or check the HTTP response headers for NUUO server signatures. Alternatively, examine physical device labels or documentation.Affected if The device is a NUUO Camera product (any model)
-
Determine the firmware versionLog into the NUUO camera web interface (usually at /) and navigate to System > Firmware/Software version, or access /config/repo.htm. For CLI access, SSH to the device and run 'cat /etc/version' or 'version' command if available.Affected if The installed firmware version is unknown, unpatched, or falls within any vulnerable version range provided by NUUO security advisories
-
Check for the vulnerable handle_config.php endpointAttempt to access http://[device-ip]/handle_config.php directly via curl or browser. A 403 or 200 response indicates the file exists. If the file responds to the 'log' parameter (e.g., ?log=test), the endpoint is active.Affected if The /handle_config.php script exists and responds to the 'log' parameter without requiring authentication
-
Verify network exposure of the deviceScan the device IP from an external network (or review firewall logs) to confirm if TCP ports 80, 443, or 8080 are open to untrusted networks. Use 'nmap -p 80,443,8080 [external-ip]' from outside the local network.Affected if The NUUO camera web interface is directly accessible from the internet or untrusted networks without VPN or firewall filtering
-
Look for indicators of compromiseReview camera system logs (if accessible via web UI or /log/ directory) for suspicious commands, reverse shell patterns, or unexpected IP connections. Check for new user accounts, unknown processes, or modified system files via SSH if available.Affected if Unexpected commands, unknown IPs, or unauthorized access patterns appear in logs or system files
You are affected if this is a NUUO Camera with an accessible /handle_config.php endpoint that does not require authentication and is exposed to untrusted networks.
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 dataRestrict network exposure of affected devices immediately; implement WAF rules to block suspicious patterns in the log parameter; contact NUUO for firmware updates; if no patch is available, consider device replacement or compensating controls such as network segmentation.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1338 — 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-1338 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