# CVE-2025-4654: Soumettre.fr <= 2.1.5 - Improper Authorization to Unauthenticated Soumettre Posts Creation/Modification/Deletion

> Unauthenticated attackers can create, edit, or delete posts in Soumettre.fr plugin when the API key is not configured.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rp73-795v-cr5f

## What is CVE-2025-4654?

CVE-2025-4654 is a low-severity missing authorization vulnerability in Soumettre.fr, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Soumettre.fr plugin for WordPress is vulnerable to unauthorized access and modification of data due to a improper authorization checks on the make_signature function in all versions up to, and including, 2.1.5. This makes it possible for unauthenticated attackers to create/edit/delete Soumettre posts. This vulnerability affects only installations where the soumettre account is not connected (i.e. API key is not installed)

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2025-4654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4654 is a low-severity missing authorization vulnerability in Soumettre.fr, published on 2 Jul 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-4654 in the wild and no public exploit code.

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

## Sources

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

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