CVE record · CVE-2022-4973

WordPress Core < 6.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via use of the_meta(); function

CVSS 4.9 MediumEPSS 0.0045 · 39th percentile

Published by the CVE Program (CNA: Wordfence) at 16 Oct 2024, 06:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
WordPress Foundation WordPress
  • affected 3.6.1 and earlier semver
  • affected 3.7 to 3.7.38, inclusive semver
  • affected 3.8 to 3.8.38, inclusive semver
  • affected 3.9 to 3.9.36, inclusive semver
  • affected 4.0 to 4.0.35, inclusive semver
  • affected 4.1 to 4.1.35, inclusive semver
  • affected 4.2 to 4.2.32, inclusive semver
  • affected 4.3 to 4.3.28, inclusive semver
  • affected 4.4 to 4.4.27, inclusive semver
  • affected 4.5 to 4.5.26, inclusive semver
  • affected 4.6 to 4.6.23, inclusive semver
  • affected 4.7 to 4.7.23, inclusive semver
  • and 13 more
Other versions: unaffected
Identifiers
CVE-2022-4973
CNA
Wordfence
Weakness (CWE)
CWE-79
Published
16 Oct 2024
Updated
8 Apr 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N CNA (Wordfence)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 16 Oct 2024. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.