Security readout for executives and security teams
Plain-English summary
GetPaid WordPress plugin versions before 2.3.4 allowed trusted-but-lower-privileged users to store scriptable content in payment form fields. If an administrator later edited or reviewed that form, the stored content could run in the admin’s browser and potentially support privilege escalation.
Executive priority
Treat as a timely plugin update for WordPress sites that use GetPaid, especially where multiple staff or external users have content roles. It is not listed as known exploited in the supplied sources.
Technical view
This is an authenticated stored cross-site scripting issue in GetPaid payment form Label and Help Text fields. The source states contributor-level users and above could create forms, and those inputs were not properly sanitized before being rendered during form editing.
Likely exposure
Exposure is limited to WordPress sites running GetPaid before 2.3.4 where contributor-or-higher accounts can create payment forms. Risk increases when administrators review forms created by less-trusted users.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires an authenticated account with sufficient permissions to create a payment form and a victim, such as an admin, later editing or reviewing it.
Researcher notes
The affected-version evidence says “before 2.3.4,” while the structured affected entry lists 2.3.4 without CPE detail. Validate against WPScan or CVE records before broad reporting. No CVSS score is supplied.
Mitigation direction
- Upgrade GetPaid to version 2.3.4 or later.
- Restrict payment form creation to trusted roles until patched.
- Review contributor and editor accounts for unnecessary privileges.
- Check vendor guidance for any additional cleanup recommendations.
Validation and detection
- Inventory WordPress sites using the GetPaid plugin.
- Confirm installed GetPaid versions are 2.3.4 or later.
- Review payment forms created by contributor-level users before patching.
- Check admin activity for unexpected actions after reviewing payment forms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-79: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-24369 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/1d1a731b-78f7-4d97-b40d-80f66700edaeCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.