# CVE-2026-19971: LB-Link WR1210M Backup Endpoint backup.cgi main missing authentication

> An attacker on the local network can access the backup endpoint without authentication, potentially reading or modifying configuration data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-68gf-2fwf-ggrm

## What is CVE-2026-19971?

CVE-2026-19971 is a medium-severity missing authorization vulnerability in LB-Link WR1210M, published on 17 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in LB-Link WR1210M 1.0.3. This impacts the function main of the file /www/cgi-bin/backup.cgi of the component Backup Endpoint. This manipulation causes missing authentication. The attack is only possible within the local network. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-19971?


## How do I fix CVE-2026-19971?

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

## Is CVE-2026-19971 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19971 and fix it if it is affected.

What it is: CVE-2026-19971 is a medium-severity missing authorization vulnerability in LB-Link WR1210M, published on 17 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19971 in the wild and no public exploit code.

Affected product: LB-Link WR1210M. 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-2026-19971/ (Markdown: https://insights.sbomify.com/CVE-2026-19971/index.md)
```

## Sources

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

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