CVE-2016-5782
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 · uneditedAn issue was discovered in Locus Energy LGate prior to 1.05H, LGate 50, LGate 100, LGate 101, LGate 120, and LGate 320. Locus Energy meters use a PHP script to manage the energy meter parameters for voltage monitoring and network configuration. The PHP code does not properly validate information that is sent in the POST request.
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 confidenceLocus Energy LGate meters (models 50, 100, 101, 120, 320 and prior to version 1.05H) contain a PHP script that manages energy meter parameters for voltage monitoring and network configuration. The PHP code fails to properly validate input data in POST requests, allowing attackers to send specially crafted requests that could manipulate device configuration or potentially execute arbitrary code.
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 dataall versionsCVSS 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
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 LGate meter modelAccess the device's web interface or check the device label/documentation to confirm the model number is one of: 50, 100, 101, 120, or 320Affected if The device model is any of 50, 100, 101, 120, or 320
-
Check the installed firmware versionLog into the LGate device management interface and navigate to the system information or firmware version section, or use the device's API/CLI to query the firmware versionAffected if The firmware version is anything other than 1.05H or later (the 'all versions' statement indicates all versions prior to 1.05H are affected)
-
Verify the PHP management script is presentAttempt to access the device's web interface and locate the PHP script used for energy meter parameter management (typically found in the device's /cgi-bin or web root directory)Affected if The PHP script for voltage monitoring and network configuration is present and accessible on the device
-
Confirm POST requests are accepted by the management interfaceSend a test POST request to the device's management endpoint using a tool like curl, checking if the device accepts and processes POST data without proper validationAffected if The device accepts unauthenticated or improperly validated POST requests to the management PHP script
The environment is affected if the device is an LGate model 50, 100, 101, 120, or 320 running firmware versions prior to 1.05H, with the PHP management script accessible and accepting POST requests without proper input validation.
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 dataUpgrade LGate firmware to version 1.05H or later, which contains proper input validation. If upgrading is not immediately possible, restrict network access to the device's management interface and monitor for suspicious POST requests.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5782 — 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-2016-5782 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