CVE-2022-1967: The WP Championship WordPress plugin before 9.3 is lacking CSRF checks in various places, allowing attackers t

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

wp-championship: upgrade to 9.3. Exact commands for each OS are on this page.

Q: Is CVE-2022-1967 being exploited?

CVE-2022-1967 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-1967 affect?

CVE-2022-1967 affects wp-championship. Severity is medium (CVSS 6.5). The WP Championship WordPress plugin before 9.3 is lacking CSRF checks in various places, allowing attackers to make a logged in admin perform unwanted actions, such as create and delete arbitrary teams as well as update the plugin's settin

Q: How urgent is CVE-2022-1967?

Priority 39/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2022-1967 is a medium-severity flaw (CVSS 6.5) affecting wp-championship. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Championship WordPress plugin before 9.3 is lacking CSRF checks in various places, allowing attackers to make a logged in admin perform unwanted actions, such as create and delete arbitrary teams as well as update the plugin's settings. Due to the lack of sanitisation and escaping, it could also lead to Stored Cross-Site Scripting issues

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-07-04
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp-championship project

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

Am I affected?

Timeline

2022-07-04 13:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

wp-championship project wp-championship UPGRADE

Affected: < 9.3

Fixed in: 9.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-championship || rpm -q wp-championship || wp-championship --version

2. UPGRADE to 9.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-championship

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-championship

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-1967?

wp-championship: upgrade to 9.3. Exact commands for each OS are on this page.

Is CVE-2022-1967 being exploited?

CVE-2022-1967 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-1967 affect?

CVE-2022-1967 affects wp-championship. Severity is medium (CVSS 6.5). The WP Championship WordPress plugin before 9.3 is lacking CSRF checks in various places, allowing attackers to make a logged in admin perform unwanted actions, such as create and delete arbitrary teams as well as update the plugin's settin

How urgent is CVE-2022-1967?

Priority 39/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs