Skip to content
Fencer Intel
medium 6.1

CVE-2022-0422 json

White Label MS < 2.2.9 - Reflected Cross-Site Scripting

published 4y ago modified 4mo ago also EUVD-2022-15564

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.1%
EPSS 8.1% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known, plus a Nuclei check

Summary

The White Label CMS WordPress plugin before 2.2.9 does not sanitise and validate the wlcms[_login_custom_js] parameter before outputting it back in the response while previewing, leading to a Reflected Cross-Site Scripting issue

Patch / fix

  • videousermanuals white_label_cms 2.2.9

Is CVE-2022-0422 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

8.08% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template WordPress White Label CMS <2.2.9 - Cross-Site Scripting nuclei detection template
  • wpscan.com https://wpscan.com/vulnerability/429be4eb-8a6b-4531-9465-9ef0d35c12cc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

  • Unknown White Label CMS

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.