# CVE-2025-2980: Legrand SMS PowerView redirect

> Remote attackers can exploit an open redirect vulnerability in Legrand SMS PowerView to redirect users to malicious sites.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-28vf-gq6v-gm54

## What is CVE-2025-2980?

CVE-2025-2980 is a medium-severity vulnerability in Legrand SMS PowerView, published on 31 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic was found in Legrand SMS PowerView 1.x. This vulnerability affects unknown code. The manipulation of the argument redirect leads to open redirect. The attack can be initiated 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-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2025-2980 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2980 is a medium-severity vulnerability in Legrand SMS PowerView, published on 31 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2980 exists.

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

## Sources

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

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