CVE-2024-11090: The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Sensitive Information Exposure

Q: How do I fix CVE-2024-11090?

restrict content: upgrade to 3.2.14. Exact commands for each OS are on this page.

Q: Is CVE-2024-11090 being exploited?

CVE-2024-11090 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-2024-11090 affect?

CVE-2024-11090 affects restrict content. Severity is medium (CVSS 5.3). The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.2.13 via the WordPress core search feature. This makes it possible for unauthenticated att

Q: How urgent is CVE-2024-11090?

Priority 33/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2024-11090 is a medium-severity flaw (CVSS 5.3) affecting restrict content. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.2.13 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-200
Published	2025-01-26
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: liquidweb

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

Am I affected?

Timeline

2025-01-26 07:15 UTCPublished CVE record published
2026-06-17 06:57 UTCUpdated Record last modified

liquidweb restrict content UPGRADE

Affected: < 3.2.14

Fixed in: 3.2.14

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy restrict-content || rpm -q restrict-content || restrict-content --version

2. UPGRADE to 3.2.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade restrict-content

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade restrict-content

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-2024-11090?

restrict content: upgrade to 3.2.14. Exact commands for each OS are on this page.

Is CVE-2024-11090 being exploited?

CVE-2024-11090 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-2024-11090 affect?

CVE-2024-11090 affects restrict content. Severity is medium (CVSS 5.3). The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.2.13 via the WordPress core search feature. This makes it possible for unauthenticated att

How urgent is CVE-2024-11090?

Priority 33/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-14844 HIGH 8.2 UPGRADE The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Missing Authentication in all v

References

← Back to latest CVEs