LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47664: WordPress Plainview Protect Passwords Plugin <= 1.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in edward_plainview Plainview Protect Passwords.This issue affects Plainview Protect Passwords: from n/a through 1.4.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF flaw in the WordPress Plainview Protect Passwords plugin through version 1.4. An attacker would need user interaction, such as luring a logged-in site user to a malicious page. The source bundle does not identify the exact affected action.

Executive priority

Treat as a moderate-priority WordPress plugin risk. Prioritize internet-facing business sites that use the plugin, but do not escalate as actively exploited based on the supplied evidence.

Technical view

CVE-2023-47664 is CWE-352 in edward_plainview Plainview Protect Passwords. The CVSS 3.1 score is 6.5 with network attack vector, low complexity, no attacker privileges, required user interaction, and high confidentiality impact. Public evidence here does not name a fixed version or specific vulnerable endpoint.

Likely exposure

Exposure is limited to WordPress sites running Plainview Protect Passwords through version 1.4. Organizations without this plugin are not indicated as affected by the supplied sources.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. CSRF generally depends on a victim using an authenticated browser session and interacting with attacker-controlled content.

Researcher notes

Key unknowns are the affected request, required victim role, fixed version, and practical impact. The CVSS vector indicates confidentiality impact, but the bundle does not explain the data exposure path.

Mitigation direction

  • Inventory WordPress sites for the Plainview Protect Passwords plugin and version.
  • Check vendor or Patchstack guidance for any fixed release or recommended workaround.
  • Disable or remove the plugin where it is unused or cannot be remediated.
  • Restrict administrative access and reinforce anti-phishing controls for WordPress users.

Validation and detection

  • Confirm whether each WordPress instance has the plugin installed and active.
  • Record plugin version and compare it with the affected range through 1.4.
  • Review plugin changelogs or vendor advisories for a documented CSRF fix.
  • Check logs for suspicious plugin-related administrative actions, where available.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

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-2023-47664 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
2Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-47664Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
edward_plainviewPlainview Protect Passwordsplainview-protect-passwords, n/aunaffected
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.