CVE-2025-1322

WP-Recall – Registration, Profile, Commerce & More <= 16.26.10 - Authenticated (Contributor+) Protected Post Disclosure

2025-03-07 00:00

Strategic Overview

Status: Patched in 16.26.12
Affected Plugin: WP-Recall – Registration, Profile, Commerce & More
Affected Version: <= 16.26.10
CVSS: 4.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2025-1322

View all WP-Recall – Registration, Profile, Commerce & More vulnerabilities

At a glance

CVE-2025-1322 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.26.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 16.26.12; sites on affected versions should update now. Disclosed March 2025, reported by Krzysztof Zając.

Vulnerability Overview

The WP-Recall – Registration, Profile, Commerce & More plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 16.26.10 via the 'feed' shortcode due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to view data from 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

WP-Recall <= 16.26.10 carries this weakness at feed, and reaching it takes an account at Contributor level or above. 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-Recall the fix is 16.26.12: builds <= 16.26.10 are affected, anything from 16.26.12 onward is not.

Remediation

Update to version 16.26.12, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP-Recall 16.26.12 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1322 https://www.wordfence.com/threat-intel/vulnerabilities/id/c667be65-e6d3-40e1-aeec-384d309fde3d https://nvd.nist.gov/vuln/detail/CVE-2025-1322

Related records

Other vulnerabilities in WP-Recall – Registration, Profile, Commerce & More

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/