CVE-2022-0499: The Sermon Browser WordPress plugin through 0.45.22 does not have CSRF checks in place when uploading Sermon f

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

sermon browser: upgrade to newer than 0.45.22. Exact commands for each OS are on this page.

Q: Is CVE-2022-0499 being exploited?

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

CVE-2022-0499 affects sermon browser. Severity is high (CVSS 8.8). The Sermon Browser WordPress plugin through 0.45.22 does not have CSRF checks in place when uploading Sermon files, and does not validate them in any way, allowing attackers to make a logged in admin upload arbitrary files such as PHP ones.

Q: How urgent is CVE-2022-0499?

Priority 48/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-0499 is a high-severity flaw (CVSS 8.8) affecting sermon browser. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Sermon Browser WordPress plugin through 0.45.22 does not have CSRF checks in place when uploading Sermon files, and does not validate them in any way, allowing attackers to make a logged in admin upload arbitrary files such as PHP ones.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-352, CWE-434
Published	2022-03-28
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: sermon browser project

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

Am I affected?

Timeline

2022-03-28 18:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

sermon browser project sermon browser UPGRADE

Affected: <= 0.45.22

Fixed in: newer than 0.45.22

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sermon-browser || rpm -q sermon-browser || sermon-browser --version

2. UPGRADE to newer than 0.45.22 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sermon-browser

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sermon-browser

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

sermon browser: upgrade to newer than 0.45.22. Exact commands for each OS are on this page.

Is CVE-2022-0499 being exploited?

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

CVE-2022-0499 affects sermon browser. Severity is high (CVSS 8.8). The Sermon Browser WordPress plugin through 0.45.22 does not have CSRF checks in place when uploading Sermon files, and does not validate them in any way, allowing attackers to make a logged in admin upload arbitrary files such as PHP ones.

How urgent is CVE-2022-0499?

Priority 48/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs