# CVE-2019-16261: Auth bypass in n/a

> Unauthenticated attackers can change admin passwords or shut off power outlets on Tripp Lite PDUs by sending POST requests to the /Forms/ directory.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 12 Sep 2019
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-q7jg-7ww6-99x3

## What is CVE-2019-16261?

CVE-2019-16261 is a critical authentication bypass vulnerability in n/a, published on 12 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tripp Lite PDUMH15AT 12.04.0053 and SU750XL 12.04.0052 devices allow unauthenticated POST requests to the /Forms/ directory, as demonstrated by changing the manager or admin password, or shutting off power to an outlet. NOTE: the vendor's position is that a newer firmware version, fixing this vulnerability, had already been released before this vulnerability report about 12.04.0053.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-16261?

It affects 1 product.


Products: Tripplite Pdumh15at Firmware.

## How do I fix CVE-2019-16261?

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

## Is CVE-2019-16261 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16261 and fix it if it is affected.

What it is: CVE-2019-16261 is a critical authentication bypass vulnerability in n/a, published on 12 Sep 2019. 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-2019-16261 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-2019-16261/ (Markdown: https://insights.sbomify.com/CVE-2019-16261/index.md)
```

## Sources

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

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