Skip to content
Noroxi
CVE-2022-45830· NVD / CVE Program· CNA Patchstack

WordPress Analytify - Google Analytics Dashboard plugin <= 4.2.3 - Privilege Escalation vulnerability

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Analytify Analytify 4.3.0.
  • Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 9.8.

Low priority for now. Upgrade to Analytify Analytify 4.3.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jan 2, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 32th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · Patchstack
6.5
3.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Is Analytify – Google Analytics 4 Tracking and Reporting in WordPress on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

Follow CVE-2022-45830

Is Analytify – Google Analytics 4 Tracking and Reporting in WordPress on your site?

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for analytify records
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
analytifyanalytify - google analytics dashboard

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • analytify analytify - google analytics dashboardbefore 4.3.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Patchstack). Independent of NVD's CPE analysis and usually ahead of it.

  • Analytify Analytify

    • n/a and later · up to and including 4.2.3affectedfixed in 4.3.0

Same product

analytify: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-26773WordPress Analytify plugin <= 5.5.0 - Broken Access Control vulnerability
    35Monitor
  • CVE-2023-41695WordPress Analytify plugin <= 5.1.0 - Broken Access Control vulnerability
    35Monitor
  • CVE-2024-35689WordPress Analytify plugin <= 5.2.3 - Cross Site Request Forgery (CSRF) vulnerability
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-47841Dec 9, 2024 · WordPress Analytify plugin <= 5.1.1 - Broken Access Control vulnerability
    17Monitor
  • ← EarlierCVE-2024-53814Dec 9, 2024 · WordPress Analytify plugin <= 5.4.3 - Broken Access Control vulnerability
    26Monitor
  • Later →CVE-2025-30897Mar 27, 2025 · WordPress Analytify plugin <= 5.5.1 - Settings Change vulnerability
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Analytify Analytify4.3.0Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-4169520 days apartWordPress Analytify plugin <= 5.1.0 - Broken Access Control vulnerability
    35Monitor
  • CVE-2025-2677346 days apartWordPress Analytify plugin <= 5.5.0 - Broken Access Control vulnerability
    35Monitor
  • CVE-2023-4784124 days apartWordPress Analytify plugin <= 5.1.1 - Broken Access Control vulnerability
    17Monitor
  • CVE-2025-3089784 days apartWordPress Analytify plugin <= 5.5.1 - Settings Change vulnerability
    17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records