CVE-2025-1504: The Post Lockdown plugin for WordPress is vulnerable to Information Exposure in all versions up to, and includ

Q: How do I fix CVE-2025-1504?

post lockdown: upgrade to newer than 4.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-1504 being exploited?

CVE-2025-1504 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1504 affect?

CVE-2025-1504 affects post lockdown. Severity is medium (CVSS 4.3). The Post Lockdown plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.0.2 via the 'pl_autocomplete' AJAX action due to insufficient restrictions on which posts can be included. This makes it po

Q: How urgent is CVE-2025-1504?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2025-1504 is a medium-severity flaw (CVSS 4.3) affecting post lockdown. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Post Lockdown plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.0.2 via the 'pl_autocomplete' AJAX action due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract data from password protected, private, or draft posts that they should not have access to.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-862
Published	2025-03-08
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: andypalmer

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-08 03:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

andypalmer post lockdown UPGRADE

Affected: <= 4.0.2

Fixed in: newer than 4.0.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy post-lockdown || rpm -q post-lockdown || post-lockdown --version

2. UPGRADE to newer than 4.0.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade post-lockdown

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade post-lockdown

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1504?

post lockdown: upgrade to newer than 4.0.2. Exact commands for each OS are on this page.

Is CVE-2025-1504 being exploited?

CVE-2025-1504 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1504 affect?

CVE-2025-1504 affects post lockdown. Severity is medium (CVSS 4.3). The Post Lockdown plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.0.2 via the 'pl_autocomplete' AJAX action due to insufficient restrictions on which posts can be included. This makes it po

How urgent is CVE-2025-1504?

Priority 22/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs