# CVE-2025-15527: WP Recipe Maker <= 10.2.2 - Insecure Direct Object Reference to Sensitive Information Exposure

> Authenticated attackers with Contributor access can expose sensitive data from private, draft, or password-protected posts via insecure direct object reference.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 16 Jan 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-h3f5-wx4v-hw9v

## What is CVE-2025-15527?

CVE-2025-15527 is a medium-severity vulnerability in brechtvds WP Recipe Maker, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Recipe Maker plugin for WordPress is vulnerable to Information Exposure in versions up to, and including, 10.2.2 via the api_get_post_summary function due to insufficient restrictions on which posts can be retrieved. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from posts they may not be able to edit or read otherwise. This also affects password protected, private, or draft posts that they should not have access to.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-15527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15527 is a medium-severity vulnerability in brechtvds WP Recipe Maker, published on 16 Jan 2026. 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-15527 exists.

Affected product: brechtvds WP Recipe Maker. 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-15527/ (Markdown: https://insights.sbomify.com/CVE-2025-15527/index.md)
```

## Sources

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

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