# CVE-2025-15490: Passster < 4.2.26 - Global Protection Bypass

> Unauthenticated attackers can bypass content protection in the Passster WordPress plugin by using crafted URLs, exposing protected resources.

- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-r64m-vg32-6jh4

## What is CVE-2025-15490?

CVE-2025-15490 is a medium-severity authentication bypass vulnerability in Unknown Passster, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Passster WordPress plugin before 4.2.26 has a flaw in its global protection checks, allowing unauthenticated users to bypass the protection offered via crafted URLs

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-15490 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15490 is a medium-severity authentication bypass vulnerability in Unknown Passster, published on 2 Sep 2026. 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-15490 exists.

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

## Sources

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

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