LiveActive security incident?Get immediate response
CVE Record

CVE-2023-27424: WordPress Inactive User Deleter Plugin <= 1.59 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Korol Yuriy aka Shra Inactive User Deleter plugin <= 1.59 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress Inactive User Deleter plugin, reported for versions up to 1.59. An attacker could potentially cause an authorized user’s browser to perform unintended plugin actions. The source bundle does not describe a specific fixed version or confirmed exploitation.

Executive priority

Treat as a routine but real WordPress plugin risk. Prioritize internet-facing business sites, sites with many administrators, and sites where unintended user-deletion behavior could disrupt operations.

Technical view

CVE-2023-27424 is CWE-352 in Korol Yuriy aka Shra Inactive User Deleter for WordPress, listed as affecting versions <= 1.59. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress sites that have the Inactive User Deleter plugin installed at an affected version. The bundle does not provide CPEs, detailed vulnerable endpoints, or exact vulnerable actions, so asset inventory confirmation is required.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Practical risk depends on whether an attacker can get a privileged WordPress user to interact with attacker-controlled content while authenticated.

Researcher notes

The provided data is sparse: it identifies CSRF, CVSS, affected plugin, and version ceiling, but not the vulnerable request, nonce failure detail, exploit maturity, or fixed release. Avoid assuming broader WordPress compromise from this CVE alone.

Mitigation direction

  • Identify WordPress sites running the Inactive User Deleter plugin.
  • Check Patchstack and vendor guidance for a fixed version or official remediation.
  • Update the plugin if a vendor-confirmed fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit WordPress administrative access to trusted users and networks.

Validation and detection

  • Inventory plugin installations and record installed versions.
  • Confirm whether any installation is version 1.59 or older.
  • Review WordPress admin activity for unexpected plugin-related changes.
  • Verify remediation against vendor or Patchstack guidance before closing.
  • Document any compensating controls if no fixed release is identified.
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-27424 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
5.4 (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:L

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-27424Attack 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:L

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
Korol Yuriy aka ShraInactive User Deleterinactive-user-deleter, 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.