CVE-2022-2628 | DSGVO All in one for WP < 4.2 - Admin+ Stored Cross-Site Scripting

Exp

The DSGVO All in one for WP WordPress plugin before 4.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

Published: 2022-10-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-2628 is rated Exploit Available (56.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.46%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2022-2628

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

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 2025-10-08 0.67% 0.46% -0.21%
2 2025-10-06 0.53% 0.67% +0.13%
3 2025-10-05 — 0.53% —

Full EPSS history (11 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.
 1.7 2.7 [email protected]

Weakness enumeration for CVE-2022-2628

OS Trackers for CVE-2022-2628

vendor priority summary link
ubuntu medium CVE-2022-2628 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-2628

Affected software / configurations for CVE-2022-2628

Vendor Product Version Raw CPE
dsgvo-for-wp dsgvo_all_in_one_for_wp < 4.2 cpe:2.3:a:dsgvo-for-wp:dsgvo_all_in_one_for_wp:*:*:*:*:*:wordpress:*:*

References for CVE-2022-2628

cvelogic Threat Intelligence