CVE-2022-3420: The Official Integration for Billingo WordPress plugin before 3.4.0 does not sanitise and escape some of its s

Q: How do I fix CVE-2022-3420?

official integration for billingo: upgrade to 3.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-3420 being exploited?

CVE-2022-3420 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3420 affect?

CVE-2022-3420 affects official integration for billingo. Severity is medium (CVSS 4.8). The Official Integration for Billingo WordPress plugin before 3.4.0 does not sanitise and escape some of its settings, which could allow high privilege users with a role as low as Shop Manager to perform Stored Cross-Site Scripting attacks.

Q: How urgent is CVE-2022-3420?

Priority 34/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2022-3420 is a medium-severity flaw (CVSS 4.8) affecting official integration for billingo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Official Integration for Billingo WordPress plugin before 3.4.0 does not sanitise and escape some of its settings, which could allow high privilege users with a role as low as Shop Manager to perform Stored Cross-Site Scripting attacks.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-10-31
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: official integration for billingo project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-31 16:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

official integration for billingo project official integration for billingo UPGRADE

Affected: < 3.4.0

Fixed in: 3.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy official-integration-for-billingo || rpm -q official-integration-for-billingo || official-integration-for-billingo --version

2. UPGRADE to 3.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade official-integration-for-billingo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade official-integration-for-billingo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3420?

official integration for billingo: upgrade to 3.4.0. Exact commands for each OS are on this page.

Is CVE-2022-3420 being exploited?

CVE-2022-3420 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3420 affect?

CVE-2022-3420 affects official integration for billingo. Severity is medium (CVSS 4.8). The Official Integration for Billingo WordPress plugin before 3.4.0 does not sanitise and escape some of its settings, which could allow high privilege users with a role as low as Shop Manager to perform Stored Cross-Site Scripting attacks.

How urgent is CVE-2022-3420?

Priority 34/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs