Wp Cerber Security\, Anti Spam \& Malware ScanWordPress extension · Cerber
CVE-2022-4712
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Cerber Security plugin for WordPress is vulnerable to stored cross-site scripting via the log parameter when logging in to the site in versions up to, and including, 9.1. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe WP Cerber Security plugin for WordPress versions up to 9.1 contains a stored XSS vulnerability. Unauthenticated attackers can inject malicious JavaScript via the login 'log' parameter, which gets stored in the plugin's log system. When administrators later view these logs in the WordPress dashboard, the injected scripts execute in their browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Cerber Security\, Anti Spam \& Malware ScanWordPress extension
< 9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Cerber Security plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Cerber Wp Cerber Security, Anti Spam & Malware Scan' or check the /wp-content/plugins/cerber-security/ directory exists on the serverAffected if The plugin is installed and active
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the WP Cerber Security plugin to view its version, or inspect the main plugin file header for the Version fieldAffected if The installed version is less than 9.2 (for example, 9.1, 9.0, 8.x, etc.)
-
Confirm logging feature is enabledGo to WP Cerber Security > Activity Log in the WordPress dashboard and verify that logging is active; alternatively, check if the cerber-log-* files exist in /wp-content/uploads/cerber/Affected if Logging is enabled and storing login attempts
-
Inspect login logs for suspicious entriesNavigate to WP Cerber Security > Activity Log in the admin panel and examine recent login entries, particularly looking for the 'log' parameter values that contain HTML, script tags, or unusual charactersAffected if Log entries contain unescaped HTML, script tags, or encoded characters that could indicate injection attempts
You are affected if WP Cerber Security plugin versions below 9.2 are installed and the logging feature is enabled, as unauthenticated XSS injection via the login log parameter can be stored and triggered when you view the logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2
Update WP Cerber Security plugin to version 9.2 or later to patch the XSS vulnerability. Until then, consider disabling the plugin or restricting admin access to the logging functions.
WP Cerber Security version 9.2 or later
- Backup the WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate WP Cerber Security plugin and click 'Update Now' to upgrade to version 9.2 or later
- Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
- Clear any cached data if a caching plugin is in use
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Cerber Security\, Anti Spam \& Malware Scan
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data