# CVE-2022-45291: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via injection in settings.php, aided by a hardcoded support password.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2023
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-gjg7-8vgp-3m7g

## What is CVE-2022-45291?

CVE-2022-45291 is a high-severity code injection vulnerability in n/a, published on 25 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PWS Personal Weather Station Dashboard (PWS_Dashboard) LTS December 2020 (2012_lts) allows remote code execution by injecting PHP code into settings.php. Attacks can use the PWS_printfile.php, PWS_frame_text.php, PWS_listfile.php, PWS_winter.php, and PWS_easyweathersetup.php endpoints. A contributing factor is a hardcoded login password of support, which is not documented. (This is not the same as the documented setup password, which is 12345.) The issue was fixed in late 2022.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-45291?

It affects 1 product.


Products: Pwsdashboard Personal Weather Station Dashboard.

## How do I fix CVE-2022-45291?

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

## Is CVE-2022-45291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45291 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45291 and fix it if it is affected.

What it is: CVE-2022-45291 is a high-severity code injection vulnerability in n/a, published on 25 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45291 exists.

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-2022-45291/ (Markdown: https://insights.sbomify.com/CVE-2022-45291/index.md)
```

## Sources

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

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