# CVE-2013-4860: Missing authorization in n/a

> Remote attackers can modify thermostat settings and network configurations without authentication due to unrestricted API access.

- **Severity:** High 8.3 (`AV:A/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xvr8-rhg7-pv7w

## What is CVE-2013-4860?

CVE-2013-4860 is a high-severity missing authorization vulnerability in n/a, published on 5 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Radio Thermostat CT80 And CT50 with firmware 1.4.64 and earlier does not restrict access to the API, which allows remote attackers to change the operation mode, wifi connection settings, temperature thresholds, and other settings via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2013-4860?

It affects 4 products.


Products: Radiothermostat Ct50, Radiothermostat Ct50 Firmware, Radiothermostat Ct80, Radiothermostat Ct80 Firmware.

## How do I fix CVE-2013-4860?

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

## Is CVE-2013-4860 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4860 and fix it if it is affected.

What it is: CVE-2013-4860 is a high-severity missing authorization vulnerability in n/a, published on 5 Jun 2014. 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-2013-4860 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-2013-4860/ (Markdown: https://insights.sbomify.com/CVE-2013-4860/index.md)
```

## Sources

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

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