# CVE-2025-6786: DocCheck Login <= 1.1.5 - Unauthorized Post Access

> Unauthenticated attackers can read password-protected posts in the DocCheck Login WordPress plugin due to improper access control implementation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Apr 2026
- **Also known as:** GHSA-73g7-fx7p-h5v2

## What is CVE-2025-6786?

CVE-2025-6786 is a medium-severity missing authorization vulnerability in antwerpes DocCheck Login, 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 DocCheck Login plugin for WordPress is vulnerable to unauthorized post access in all versions up to, and including, 1.1.5. This is due to plugin redirecting a user to login on a password protected post after the page has loaded. This makes it possible for unauthenticated attackers to read posts they should not have access to.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-6786 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6786 is a medium-severity missing authorization vulnerability in antwerpes DocCheck Login, published on 4 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-6786 in the wild and no public exploit code.

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

## Sources

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

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