LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45830: WordPress Analytify - Google Analytics Dashboard plugin <= 4.2.3 - Privilege Escalation vulnerability

Missing Authorization vulnerability in Analytify.This issue affects Analytify: from n/a through 4.2.3.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Analytify Google Analytics Dashboard plugin through version 4.2.3. The reported issue is missing authorization, allowing privilege escalation impact on affected sites. Business risk is moderate because it is network-accessible and requires no prior privileges, but the provided sources do not cite active exploitation.

Executive priority

Prioritize remediation in the next normal vulnerability cycle, faster for externally exposed WordPress sites with user registration or delegated administration. Escalate if vendor guidance or monitoring later confirms exploitation.

Technical view

CVE-2022-45830 is a CWE-862 missing authorization flaw in Analytify wp-analytify through 4.2.3. CVSS 3.1 is 6.5, with network attack vector, low complexity, no privileges, and no user interaction. Reported impact is low integrity and low availability, with no confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites using the Analytify plugin at version 4.2.3 or earlier. The source bundle does not provide install prevalence, affected endpoints, or a confirmed fixed version.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. The CVSS vector indicates unauthenticated network reachability, which raises triage priority despite incomplete technical detail.

Researcher notes

Available evidence names missing authorization and privilege escalation but does not include affected code paths, proof details, exploit status, or fixed version. Treat validation as inventory-driven and avoid assuming exploit mechanics beyond the CVSS vector and CWE.

Mitigation direction

  • Inventory WordPress sites for the wp-analytify plugin and version.
  • Check Analytify and Patchstack guidance for a vendor-confirmed fixed version.
  • Upgrade when vendor-confirmed remediation is identified.
  • Disable or remove the plugin where acceptable until remediation is confirmed.
  • Review WordPress user roles for unexpected privilege changes.

Validation and detection

  • Confirm all WordPress instances running wp-analytify are identified.
  • Verify whether any instance uses Analytify version 4.2.3 or earlier.
  • Review administrator and privileged user accounts for unauthorized changes.
  • Check security monitoring for suspicious WordPress account or role activity.
  • Track CVE and Patchstack records for updated remediation details.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-45830 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
6.5 (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
6.5CVSS 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

6.5Medium
CVSS 3.1 vector shape for CVE-2022-45830Attack 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
AnalytifyAnalytifywp-analytify, n/aunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.