Security readout for executives and security teams
Plain-English summary
A WordPress Forms plugin before 1.12.3 allowed an authenticated user to save unsafe script content in a form field. When another user viewed the stored content, browser-side code could run in that user’s session. This is most concerning on sites where lower-privileged accounts can access form-building features.
Executive priority
Treat this as a targeted cleanup item for WordPress estates, not an emergency based on current evidence. Prioritize public sites with delegated content or form-management access.
Technical view
CVE-2021-24505 is a CWE-79 authenticated stored XSS issue in the Forms WordPress plugin. The source bundle says input fields, specifically the Forms “Add new” field, were not sanitized before version 1.12.3. No CVSS vector, detailed privilege requirement, or exploit detail is provided.
Likely exposure
Exposure is limited to WordPress sites using the affected Forms plugin before 1.12.3, especially where non-administrators can create or edit forms. Sites without this plugin are not affected based on the provided sources.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as KEV. Because this is stored XSS, impact depends on who can save malicious content and who later views it.
Researcher notes
Evidence is sparse: the bundle identifies authenticated stored XSS and the vulnerable area but omits CVSS, affected role granularity, exploitability details, and confirmation of exploitation. Avoid assuming impact beyond browser-side code execution through stored form content.
Mitigation direction
- Inventory WordPress sites for the Forms plugin and installed version.
- Upgrade affected installations to version 1.12.3 or later.
- Restrict form creation and editing to trusted roles.
- Review vendor guidance before applying compensating controls.
- Remove the plugin if it is unused or cannot be updated.
Validation and detection
- Confirm whether the Forms plugin is installed on each WordPress site.
- Check that installed versions are 1.12.3 or later.
- Review user roles with access to Forms creation or editing.
- Inspect recent form changes for unexpected script-like content.
- Verify stored form fields render safely after updating.
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 lookupCVE-2021-24505 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/550e08ac-4c3a-4e22-8e98-bc5bfc020ca9CVE reference · x_refsource_MISC
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.