CVE-2025-15527

WP Recipe Maker <= 10.2.2 - Insecure Direct Object Reference to Sensitive Information Exposure

2025-12-11 20:23

Strategic Overview

Status: Patched in 10.2.3
Affected Plugin: WP Recipe Maker
Affected Version: <= 10.2.2
CVSS: 4.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2025-15527

View all WP Recipe Maker vulnerabilities

At a glance

CVE-2025-15527 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Recipe Maker WordPress plugin, affecting versions <= 10.2.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 10.2.3; sites on affected versions should update now. Disclosed December 2025, reported by Dmitrii Ignatyev.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

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

Reaching this weakness in WP Recipe Maker <= 10.2.2 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Recipe Maker the fix is 10.2.3: builds <= 10.2.2 are affected, anything from 10.2.3 onward is not.

Remediation

Update to version 10.2.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP Recipe Maker 10.2.3 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-15527 https://www.wordfence.com/threat-intel/vulnerabilities/id/96f77fdc-4e91-43c0-8bc6-7bb202945c7d https://nvd.nist.gov/vuln/detail/CVE-2025-15527

Related records

Other vulnerabilities in WP Recipe Maker

CVSS Vector

4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/