CVE-2026-2550
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 EFM iptime A6004MX 14.18.2. Affected is the function commit_vpncli_file_upload of the file /cgi/timepro.cgi. The manipulation results in unrestricted upload. The attack may be performed from remote. The exploit has been made public and could 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 · high confidenceUnrestricted file upload vulnerability in the commit_vpncli_file_upload function of /cgi/timepro.cgi on EFM iptime A6004MX router firmware 14.18.2 allows remote attackers to upload arbitrary files, potentially achieving remote code execution. The CVSS 9.8 score indicates trivial network exploitation with complete system compromise potential.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify device model and firmware versionAccess the router admin web interface and navigate to System > Firmware or Status page to view the installed firmware version. Alternatively, check the label on the device or the admin interface header for the firmware build number.Affected if The firmware version is 14.18.2 or matches the vulnerable release.
-
Confirm timepro.cgi is presentAttempt to access the CGI endpoint directly by navigating to http://<router-ip>/cgi/timepro.cgi in a browser or via curl. A 200 OK response indicates the web interface is active.Affected if The endpoint responds, indicating the vulnerable CGI script is present and accessible.
-
Verify the web management interface is enabledCheck if the router web interface is running on ports 80 or 443 by scanning the device with nmap: nmap -p 80,443 <router-ip> or by attempting a connection.Affected if Ports 80 or 443 are open and the web interface is reachable.
-
Assess network exposureDetermine if the router management interface is accessible from external networks by checking NAT/firewall rules, port forwarding configurations, or by attempting access from outside the local network.Affected if The device web interface is exposed to untrusted networks (WAN accessible) rather than isolated to a trusted LAN.
The device is affected if it is an EFM iptime A6004MX running firmware 14.18.2, the /cgi/timepro.cgi endpoint is accessible, and the router web 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.
From vendor dataImplement network segmentation to isolate the affected device, block external access to the web interface (port 80/443), and consider replacing the device since the unresponsive vendor likely will not provide a patch. If the vulnerable function can be disabled without impacting operations, do so.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2550 — 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-2026-2550 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