# CVE-2025-1341: PMWeb Setting weak password

> Weak password requirements in PMWeb allow attackers to bypass security controls, requiring configuration changes to enforce stronger policies.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-2f9p-v3x6-jqrm

## What is CVE-2025-1341?

CVE-2025-1341 is a medium-severity vulnerability in PMWeb, published on 16 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in PMWeb 7.2.0. This affects an unknown part of the component Setting Handler. The manipulation leads to weak password requirements. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Pmweb Pmweb.

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

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

## Is CVE-2025-1341 being exploited?

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

## Other vulnerabilities in PMWeb

- [CVE-2024-7466](https://insights.sbomify.com/CVE-2024-7466/): PMWeb Web Application Firewall cross site scripting (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1341 is a medium-severity vulnerability in PMWeb, published on 16 Feb 2025. 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-2025-1341 in the wild and no public exploit code.

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

## Sources

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

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