# CVE-2025-5920: Sharable Password Protected Posts < 1.1.1 - Unauthenticated Password Protect Post Access

> Unauthenticated attackers can access password-protected posts by retrieving the secret key from the REST API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 4 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-c2r3-hccf-qqvp

## What is CVE-2025-5920?

CVE-2025-5920 is a high-severity vulnerability in Unknown Sharable Password Protected Posts, published on 4 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sharable Password Protected Posts before version 1.1.1 allows access to password protected posts by providing a secret key in a GET parameter. However, the key is exposed by the REST API.

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

It affects 1 product.


Products: Fabiantodt Private Post Share.

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

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

## Is CVE-2025-5920 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5920 is a high-severity vulnerability in Unknown Sharable Password Protected Posts, published on 4 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5920 exists.

Affected product: Unknown Sharable Password Protected Posts. 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-5920/ (Markdown: https://insights.sbomify.com/CVE-2025-5920/index.md)
```

## Sources

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

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