# CVE-2025-9544: Doppler Forms <= 2.5.1 - Subscriber+ Limited Plugin Installation

> Authenticated subscribers can install and activate whitelisted Doppler Forms extensions due to missing capability checks in an AJAX handler.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A: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:** 29 Oct 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-f6mm-28jx-rrww

## What is CVE-2025-9544?

CVE-2025-9544 is a medium-severity missing authorization vulnerability in Unknown Doppler Forms, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Doppler Forms WordPress plugin through 2.5.1 registers an AJAX action install_extension without verifying user capabilities or using a nonce. As a result, any authenticated user — including those with the Subscriber role — can install and activate additional Doppler Forms WordPress plugin through 2.5.1 (limited to those whitelisted by the main Doppler Forms WordPress plugin through 2.5.1).

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


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

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

## Is CVE-2025-9544 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9544 is a medium-severity missing authorization vulnerability in Unknown Doppler Forms, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9544 exists.

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

## Sources

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

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