CVE-2022-43497

Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7.

Published: 2022-12-05 Last update: 2025-04-24 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-43497 is rated Moderate Risk (53.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.72%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-43497

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-14 1.52% 1.72% +0.20%
2 2026-01-26 0.88% 1.52% +0.64%
3 2025-12-28 — 0.88% —

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-43497

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-43497

OS Trackers for CVE-2022-43497

vendor priority summary link
debian not yet assigned CVE-2022-43497 not yet assigned priority: Debian including 1 source packages (wordpress), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-43497
ubuntu medium CVE-2022-43497 medium priority: Ubuntu including 1 source packages (wordpress), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 6. https://ubuntu.com/security/CVE-2022-43497

Affected software / configurations for CVE-2022-43497

Vendor Product Version Raw CPE
wordpress wordpress < 3.7.40 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 3.8, < 3.8.40 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 3.9, < 3.9.39 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.0, < 4.0.37 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.1, < 4.1.37 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.2, < 4.2.34 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.3, < 4.3.30 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.4, < 4.4.29 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.5, < 4.5.28 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.6, < 4.6.25 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.7, < 4.7.25 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.8, < 4.8.21 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 4.9, < 4.9.22 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.0, < 5.0.18 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.1, < 5.1.15 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.2, < 5.2.17 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.3, < 5.3.14 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.4, < 5.4.12 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.5, < 5.5.11 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.6, < 5.6.10 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.7, < 5.7.8 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.8, < 5.8.6 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 5.9, < 5.9.5 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpress wordpress >= 6.0, < 6.0.3 cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*

References for CVE-2022-43497

cvelogic Threat Intelligence