dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-34104

CRITICAL · 9.4 CVSS v4.0 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
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.

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 · high confidence

An authenticated remote code execution vulnerability in Piwik/Matomo versions before 3.0.3 allows a Superuser to upload a malicious plugin as a ZIP archive containing arbitrary PHP code, which gets executed on the server. The plugin upload mechanism lacks sufficient validation, enabling code execution through a specially crafted plugin.

MitigationUpgrade to Matomo 3.0.3 or later, which disables plugin upload by default. If plugin upload functionality is required, explicitly enable it in the configuration file with appropriate access controls and validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Matomo/Piwik installation and version
    Locate the Matomo installation and check the version. The version is typically displayed in the Matomo dashboard (Admin > Diagnostics > System Check) or can be found in a version file at the root of the Matomo installation.
    Affected if The installed version is before 3.0.3
  2. Confirm Superuser authentication status
    Determine if the user performing checks or the target user has Superuser privileges in Matomo. This vulnerability requires Superuser access.
    Affected if The authenticated user has Superuser privileges
  3. Check plugin upload configuration
    Inspect the Matomo configuration file (config/config.ini.php) for plugin upload settings. Look for parameters related to plugin upload functionality.
    Affected if Plugin upload is enabled and the version is before 3.0.3
  4. Verify plugin upload is accessible
    Navigate to the plugin upload interface in Matomo admin (Admin > Marketplace > Upload a plugin) to confirm the feature is available and accessible to Superusers.
    Affected if Plugin upload feature is enabled and accessible to Superusers

A user is affected if they are running Matomo/Piwik version before 3.0.3 AND have plugin upload enabled with Superuser access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Matomo 3.0.3 or later, which disables plugin upload by default. If plugin upload functionality is required, explicitly enable it in the configuration file with appropriate access controls and validation.

Recommended fix High confidence

Matomo 3.0.3 or later stable release

  1. 1. Backup your Matomo/Piwik database and configuration files before upgrading.
  2. 2. Download Matomo 3.0.3 or a later stable release from the official Matomo repository (github.com/matomo-org/matomo/releases).
  3. 3. Replace the existing Matomo/Piwik files with the new version, preserving your config/config.ini.php file.
  4. 4. Run the Matomo database upgrade process by accessing your Matomo URL and following the upgrade wizard.
  5. 5. After upgrade, verify that the plugin upload functionality is disabled by default (this is the default behavior in 3.0.3+).
  6. 6. If plugin upload is explicitly needed, enable it carefully in config/config.ini.php with proper access controls.
Caveat Minor - this is a relatively old version jump; ensure plugin compatibility with PHP version and review config changes between your current version and 3.0.3

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34104 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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