CVE-2022-3907: The Clerk WordPress plugin before 4.0.0 is affected by time-based attacks in the validation function for all A

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

clerk.io: upgrade to 4.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-3907 being exploited?

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

CVE-2022-3907 affects clerk.io. Severity is high (CVSS 7.5). The Clerk WordPress plugin before 4.0.0 is affected by time-based attacks in the validation function for all API requests due to the usage of comparison operators to verify API keys against the ones stored in the site options.

Q: How urgent is CVE-2022-3907?

Priority 51/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

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

The Clerk WordPress plugin before 4.0.0 is affected by time-based attacks in the validation function for all API requests due to the usage of comparison operators to verify API keys against the ones stored in the site options.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-203
Published	2022-12-05
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: clerk.io

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

Am I affected?

Timeline

2022-12-05 17:15 UTCPublished CVE record published
2026-06-17 05:00 UTCUpdated Record last modified

clerk.io clerk.io UPGRADE

Affected: < 4.0.0

Fixed in: 4.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy clerk.io || rpm -q clerk.io || clerk.io --version

2. UPGRADE to 4.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade clerk.io

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade clerk.io

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

clerk.io: upgrade to 4.0.0. Exact commands for each OS are on this page.

Is CVE-2022-3907 being exploited?

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

CVE-2022-3907 affects clerk.io. Severity is high (CVSS 7.5). The Clerk WordPress plugin before 4.0.0 is affected by time-based attacks in the validation function for all API requests due to the usage of comparison operators to verify API keys against the ones stored in the site options.

How urgent is CVE-2022-3907?

Priority 51/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs