LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4385: WP Private Content Plus <= 3.1 - Cross-Site Request Forgery Bypass

The WP Private Content Plus plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1. This is due to missing or incorrect nonce validation on the save_groups() function. This makes it possible for unauthenticated attackers to add new group members via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

This vulnerability affects the WP Private Content Plus WordPress plugin up to version 3.1. If a logged-in administrator is tricked into interacting with a malicious request, an outside attacker may add group members. Business impact is limited but relevant where private content groups control access to sensitive material.

Executive priority

Handle in normal vulnerability maintenance unless the plugin protects sensitive or paid content. Prioritize affected public-facing WordPress sites, but this is below emergency patching because user interaction is required and no active exploitation is cited.

Technical view

CVE-2021-4385 is a CSRF issue in save_groups() caused by missing or incorrect nonce validation. The reported impact is low-integrity modification: unauthenticated attackers can submit forged requests that add group members when an administrator performs the required user interaction.

Likely exposure

Exposure is limited to WordPress sites running WP Private Content Plus at version 3.1 or earlier. Risk is higher where administrators are frequently logged in and private content groups gate customer, employee, or paid-access content.

Exploitation context

The CVE is not listed in KEV, and the supplied sources do not show active exploitation. Exploitation requires social engineering of a site administrator, so this is not an unauthenticated direct compromise path.

Researcher notes

The source bundle contains an inconsistency: the narrative states versions up to 3.1 are vulnerable, while the affected metadata is sparse and lists version 0 with default unaffected. Use the CVE description, Wordfence entry, and WordPress changeset as primary evidence, then verify vendor release history.

Mitigation direction

  • Inventory WordPress sites for WP Private Content Plus installations.
  • Update affected installations beyond version 3.1 where vendor guidance confirms a fix.
  • If no fixed release is available, disable the plugin until vendor guidance is clear.
  • Limit WordPress administrator sessions and access to trusted users only.
  • Warn administrators against opening unsolicited links while logged into WordPress.

Validation and detection

  • Check each WordPress site for the plugin name and installed version.
  • Treat version 3.1 or earlier as potentially affected based on the CVE description.
  • Review group membership records for unexpected additions.
  • Review administrative activity logs around private content group changes.
  • Confirm current plugin code includes nonce validation for group-saving actions.
Prepared
Confidence
medium
Sources
6

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4385 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-4385Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nimeshrmrWP Private Content Plus0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.