# CVE-2025-2982: Legrand SMS PowerView file inclusion

> Remote attackers can exploit a file inclusion vulnerability in Legrand SMS PowerView to execute code or read sensitive data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-jpmx-qvrq-8c62

## What is CVE-2025-2982?

CVE-2025-2982 is a medium-severity path traversal vulnerability in Legrand SMS PowerView, published on 31 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Legrand SMS PowerView 1.x. Affected is an unknown function. The manipulation of the argument redirect leads to file inclusion. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2025-2982?


## How do I fix CVE-2025-2982?

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

## Is CVE-2025-2982 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2982 and fix it if it is affected.

What it is: CVE-2025-2982 is a medium-severity path traversal vulnerability in Legrand SMS PowerView, published on 31 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2982 in the wild and no public exploit code.

Affected product: Legrand SMS PowerView. 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-2025-2982/ (Markdown: https://insights.sbomify.com/CVE-2025-2982/index.md)
```

## Sources

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

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