SitealertWordPress extension
CVE-2022-46857
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in SiteAlert plugin <= 1.9.7 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the SiteAlert WordPress plugin affecting versions 1.9.7 and below. The vulnerability allows attackers to potentially trick authenticated administrators into performing unintended actions via maliciously crafted requests.
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
SitealertWordPress extension
<= 1.9.7CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 SiteAlert plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Sitealert Sitealert' or 'SiteAlert', or inspect the plugin directory at wp-content/plugins/sitealert/ for the main plugin fileAffected if SiteAlert plugin is not installed or not present in the plugins directory
-
Determine installed versionCheck the plugin header in sitealert.php or the Plugins page in WordPress admin for the version numberAffected if Version is 1.9.7 or lower
-
Inspect forms for nonce field presenceExamine the plugin PHP files for forms (HTML forms) and check if they include wp_nonce_field() function calls generating nonce fieldsAffected if Forms exist in the plugin but do not contain wp_nonce_field() or equivalent nonce generation
-
Verify nonce validation on form processingSearch plugin source code for wp_verify_nonce(), check_admin_referer(), or wp_create_nonce() calls where form submissions are processedAffected if Form processing code exists without nonce verification logic
-
Check AJAX actions for nonce verificationLook for add_action('wp_ajax_') or add_action('wp_ajax_nopriv_') calls and verify if the handler functions call wp_verify_nonce() or check_admin_referer() before processingAffected if AJAX handlers exist but do not validate nonces before executing state-changing operations
If SiteAlert plugin version 1.9.7 or lower is installed AND its forms or AJAX actions lack nonce verification (wp_verify_nonce/check_admin_referer), the environment is vulnerable to CVE-2022-46857.
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.
From vendor dataImplement anti-CSRF tokens (nonces) using WordPress nonce functions (wp_nonce_field/wp_verify_nonce) on all forms and AJAX actions within the plugin, and ensure all state-changing operations validate these tokens.
Fix this in Sitealert
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46857 — 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-46857 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