CVE-2019-7268
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 · uneditedLinear eMerge 50P/5000P devices allow Unauthenticated File Upload.
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 confidenceThe Linear eMerge 50P and 5000P physical security devices contain an unauthenticated file upload vulnerability that allows remote attackers to upload arbitrary files to the device without any authentication credentials, likely enabling remote code execution.
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<= 4.6.07<= 4.6.07CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the device modelAccess the device web interface or check physical device labeling. The Linear eMerge 50P and 5000P are physical security access control panels. Navigate to the admin/login page or system information page to confirm the exact model number displayed by the device.Affected if The device is a Nortekcontrol Linear eMerge 50P or 5000P physical security device.
-
Check the firmware versionLog into the device web interface and navigate to the firmware or system information section. The firmware version is typically displayed under settings like 'System Info', 'About', or 'Firmware Version'. Compare the installed version against the affected range.Affected if The firmware version is 4.6.07 or lower.
-
Determine if the web management interface is network-accessibleCheck network segmentation and firewall rules. Identify the IP address assigned to the device and verify which network segments can reach TCP ports 80 (HTTP) or 443 (HTTPS) on the device. Use network scanning tools or review firewall configuration to confirm exposure.Affected if The device web interface is accessible from untrusted network segments or the internet.
-
Inspect for unauthorized files or scriptsIf you have administrative access, review the device file system for unexpected uploaded files. Check common web directories (document root, uploads folder, cgi-bin) for unfamiliar PHP, JSP, ASP, or shell script files that were not deployed by your organization.Affected if Unexpected executable files or scripts exist on the device that were not intentionally deployed.
The environment is affected if a Linear eMerge 50P or 5000P device is running firmware version 4.6.07 or lower and its web interface is accessible from untrusted network segments, as the unauthenticated file upload vulnerability can be exploited without credentials.
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 dataIsolate affected devices on a restricted network segment with firewall controls limiting access to trusted management IPs; implement intrusion detection monitoring for suspicious upload activity; contact vendor for firmware patches.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.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,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7268 — 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-2019-7268 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