LiveActive security incident?Get immediate response
CVE Record

CVE-2022-46857: WordPress SiteAlert (Formerly WP Health) Plugin <= 1.9.7 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in SiteAlert plugin <= 1.9.7 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-46857 is a CSRF issue in the WordPress SiteAlert plugin, formerly WP Health, affecting versions 1.9.7 and earlier. An attacker could potentially cause limited unauthorized changes if a site operator’s browser is abused. The public record rates this as medium severity, not an emergency-level compromise.

Executive priority

Handle through normal vulnerability management with near-term WordPress plugin inventory and remediation tracking. Escalate only for important public-facing WordPress sites where the affected plugin is confirmed and no fixed release is available.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in the WordPress plugin package my-wp-health-check. The CVSS 3.1 score is 5.4 with low attack complexity and low integrity and availability impact. The source bundle does not describe the vulnerable endpoint, exact action, fixed version, or exploit mechanics.

Likely exposure

Exposure is limited to WordPress sites with the SiteAlert plugin installed at version 1.9.7 or earlier. Sites not using this plugin are not indicated as affected by the supplied sources.

Exploitation context

The CVE is not listed in CISA KEV, and the supplied sources do not state active exploitation. The available evidence supports treating this as a known plugin weakness requiring inventory and vendor-guidance follow-up.

Researcher notes

Public details are sparse. The source bundle confirms CSRF, affected versions through 1.9.7, CWE-352, and CVSS 5.4. It does not identify the vulnerable action, nonce failure details, authentication assumptions, exploit status, or fixed version.

Mitigation direction

  • Inventory WordPress sites for the SiteAlert or my-wp-health-check plugin.
  • Check SiteAlert, WordPress plugin, or Patchstack guidance for a fixed release.
  • Apply the vendor-recommended update if a fixed version is confirmed.
  • If no fix is confirmed, evaluate temporary disablement based on business need.
  • Monitor WordPress admin activity for unexpected plugin-related changes.

Validation and detection

  • Confirm whether any site runs SiteAlert version 1.9.7 or earlier.
  • Record plugin package name my-wp-health-check during asset checks.
  • Review Patchstack and CVE records for fixed-version details.
  • Verify remediation by confirming the installed plugin version after changes.
  • Check whether plugin functionality is still required on exposed sites.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-46857 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-46857Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiteAlertSiteAlertmy-wp-health-check, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.