LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24328: WP Login Security and History <= 1.0 - CSRF to Stored Cross-Site Scripting (XSS)

The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin's settings to arbitrary values, and set XSS payloads on them as well

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress login plugin could accept settings changes made through an administrator’s browser without proving the admin intended them. If an admin was tricked while logged in, malicious script could be stored in plugin settings. Sources do not provide CVSS, a fixed version, or confirmed exploitation evidence.

Executive priority

Treat this as a targeted WordPress admin-risk issue, not a confirmed internet-wide emergency. Prioritize sites using the affected plugin, especially externally administered or high-value WordPress properties.

Technical view

WP Login Security and History through 1.0 lacked CSRF protection when saving settings and did not sanitize or validate those settings. The reported impact is CSRF leading to stored XSS in plugin configuration values, affecting administrator-driven WordPress workflows.

Likely exposure

Exposure appears limited to WordPress sites running WP Login Security and History version 1.0 or earlier. The bundle does not identify other affected products, CPEs, or later vulnerable versions.

Exploitation context

The described attack depends on a logged-in administrator being induced to trigger a settings change. KEV is false, and the provided sources do not confirm active exploitation in the wild.

Researcher notes

Evidence is sparse: no CVSS vector, no vendor fix details, and no KEV listing. The core issue is missing CSRF validation plus absent settings sanitization, producing stored XSS through administrator-mediated configuration changes.

Mitigation direction

  • Inventory WordPress sites for WP Login Security and History version 1.0 or earlier.
  • Check vendor or plugin repository guidance for fixed, retired, or unsupported status.
  • Disable or remove the affected plugin if no maintained fix is available.
  • Limit administrator sessions and reinforce admin phishing protections.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version and compare it with the affected 1.0 scope.
  • Review plugin settings for unexpected values or script-like content.
  • Check WordPress admin activity for suspicious settings changes.
Prepared
Confidence
medium
Sources
5

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-2021-24328 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownWP Login Security and History1.0Listed
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.