CVE-2016-0867
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 · uneditedCAREL PlantVisorEnhanced allows remote attackers to bypass intended access restrictions via a direct file 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 confidenceCAREL PlantVisorEnhanced, a building management system web application, contains an access control bypass vulnerability where remote attackers can directly request specific files to bypass intended authentication and authorization restrictions. The vulnerability allows unauthenticated access to sensitive resources through direct file paths without proper access validation.
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 if PlantVisorEnhanced is installedCheck for the CAREL PlantVisorEnhanced web application by reviewing installed software, scanning for the application on the network, or checking for the application's web interface on common ports (typically port 80/443). Look for the PlantVisor login page or application files on the system.Affected if The application is present and running on the network or system.
-
Verify authentication is enforced on the main login pageAttempt to access the PlantVisorEnhanced login page via HTTP/HTTPS and confirm that the application presents a login form requiring credentials before granting access to protected resources.Affected if The login page is directly accessible without credentials, which is expected behavior for the login page itself.
-
Test direct file path access without credentialsUsing a web browser or HTTP tool (such as curl), attempt to directly request common sensitive file paths such as configuration files, data logs, or system files that would normally require authentication. Example paths may include: /data/, /config/, /logs/, /backup/, or other application-specific directories that might contain sensitive information.Affected if Direct access to sensitive files or directories is granted without requiring any authentication credentials.
-
Check for unauthenticated API or endpoint accessIf the application exposes any API endpoints, direct URLs, or file handlers, attempt to access these endpoints directly without providing any authentication tokens or session cookies.Affected if The application returns sensitive data or allows access to protected functionality without any authentication.
-
Review access control configurationExamine the application's configuration files or web server settings (if accessible) to determine whether proper authentication and authorization checks are implemented on all file request handlers. Look for missing access control rules or misconfigured permissions.Affected if Configuration shows that file request handlers lack proper authentication validation logic.
If PlantVisorEnhanced is running and direct file paths or sensitive resources can be accessed without providing any authentication credentials, the environment is affected by this access control bypass vulnerability.
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 proper authentication and authorization checks on all file request handlers, ensuring that every direct file access validates user credentials and permissions before serving content. Consider implementing role-based access control (RBAC) and conducting access control testing across all application endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0867 — 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-0867 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