Security readout for executives and security teams
Plain-English summary
This is a WordPress core stored XSS issue affecting sites before the 6.0.2 security release. A logged-in user with post or page editing access, such as Contributor or higher, could store script content that runs when a page uses the_meta(). Business risk is moderate because exploitation needs account access and a specific rendering path.
Executive priority
Treat as a scheduled security update unless the site allows untrusted contributors or uses custom templates that expose metadata. Prioritize faster remediation for publishing platforms, community sites, or any WordPress environment with broad editor access.
Technical view
CVE-2022-4973 is CWE-79 in WordPress core. The issue allows authenticated Contributor+ users to inject stored scripts into posts or pages when the_meta() renders affected metadata. CVSS 3.1 is 4.9 with low privileges, high attack complexity, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely on WordPress sites running affected core versions before 6.0.2, with users allowed to edit posts or pages, and themes or templates that call the_meta(). Sites with many third-party contributors have higher practical risk.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The attack requires an authenticated editing role and depends on the vulnerable content being rendered through the_meta(), so this is not described as unauthenticated mass exploitation.
Researcher notes
Evidence supports a conditional stored XSS in WordPress core tied to the_meta(). The record’s title indicates versions before 6.0.2, while the description wording says up to 6.0.2; use vendor release information and the referenced changeset to confirm fixed builds.
Mitigation direction
- Upgrade WordPress core to version 6.0.2 or later.
- Review vendor guidance from WordPress and Wordfence for related security notes.
- Limit Contributor, Author, and Editor access to trusted accounts.
- Remove or review unnecessary templates that render post metadata with the_meta().
- Audit existing contributed content for suspicious stored script content.
Validation and detection
- Inventory WordPress core versions and flag installs before 6.0.2.
- Identify themes or templates that call the_meta().
- Review accounts with Contributor, Author, or Editor permissions.
- Confirm production sites received the 6.0.2 security release or newer.
- Check security monitoring for suspicious post or metadata changes.
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-2022-4973 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
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
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 vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N1.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b5582e89-83e6-4898-b9fe-09eddeb5f7ae?source=cveCVE reference
- https://core.trac.wordpress.org/changeset/53961CVE reference
- https://wordpress.org/news/2022/08/wordpress-6-0-2-security-and-maintenance-release/CVE reference
- https://www.wordfence.com/blog/2022/08/wordpress-core-6-0-2-security-maintenance-release-what-you-need-to-know/CVE reference
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.