# CVE-2016-2275: Missing authorization in n/a

> Remote attackers can perform administrative actions on Advantech SmartWorx devices by bypassing client-side JavaScript access controls.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fphg-vqgv-6r7j

## What is CVE-2016-2275?

CVE-2016-2275 is a critical missing authorization vulnerability in n/a, published on 21 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface on Advantech/B+B SmartWorx VESP211-EU devices with firmware 1.7.2 and VESP211-232 devices with firmware 1.5.1 and 1.7.2 relies on the client to implement access control, which allows remote attackers to perform administrative actions via modified JavaScript code.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-2275?

It affects 2 products.


Products: Advantech Vesp211-232 Firmware, Advantech Vesp211-Eu Firmware.

## How do I fix CVE-2016-2275?

No fix has been published for CVE-2016-2275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-2275 being exploited?

There is no known exploitation of CVE-2016-2275 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2275 and fix it if it is affected.

What it is: CVE-2016-2275 is a critical missing authorization vulnerability in n/a, published on 21 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2275 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2275/ (Markdown: https://insights.sbomify.com/CVE-2016-2275/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2275
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2275
- OSV: https://osv.dev/vulnerability/CVE-2016-2275

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2275/
Summaries are generated and may contain mistakes; the official description above is the record.