dbcve.org
Tikiwiki Cms\/groupwareApplication · Tiki

CVE-2025-34111

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to after 15.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 unauthenticated arbitrary file upload vulnerability exists in Tiki Wiki CMS Groupware version 15.1 and earlier via the ELFinder component's default connector (connector.minimal.php), which allows remote attackers to upload and execute malicious PHP scripts in the context of the web server. The vulnerable component does not enforce file type validation, allowing attackers to craft a POST request to upload executable PHP payloads through the ELFinder interface exposed at /vendor_extra/elfinder/.

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

Unauthenticated arbitrary file upload vulnerability in Tiki Wiki CMS Groupware <=15.1 allows remote attackers to upload malicious PHP scripts via the ELFinder component's default connector (connector.minimal.php) at /vendor_extra/elfinder/. The connector lacks file type validation, enabling execution of uploaded payloads in the web server context.

MitigationDisable or restrict access to the ELFinder connector at /vendor_extra/elfinder/ until a patch is applied; alternatively, upgrade to a patched Tiki Wiki version that enforces proper file type validation in the ELFinder component.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tikiwiki Cms\/groupwareApplication
Affected:<= 15.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Tiki Wiki version
    Check the version number in your Tiki Wiki installation (typically visible in the admin panel or in version files within the installation directory)
    Affected if The installed version is 15.1 or any earlier version of Tiki Wiki CMS Groupware
  2. Verify ELFinder connector presence
    Check if the directory /vendor_extra/elfinder/ exists in your Tiki Wiki web root
    Affected if The /vendor_extra/elfinder/ directory exists in the installation
  3. Confirm connector file accessibility
    Attempt to access /vendor_extra/elfinder/connector.minimal.php via an HTTP request to your server
    Affected if The connector.minimal.php file responds or is reachable over the network
  4. Assess PHP execution capability
    Check the web server configuration to determine if PHP execution is allowed in the directories where ELFinder stores uploaded files
    Affected if PHP files can be executed from the ELFinder upload directories

Your environment is affected if you are running Tiki Wiki version 15.1 or earlier AND the ELFinder connector at /vendor_extra/elfinder/connector.minimal.php is accessible and PHP execution is permitted in its upload directories

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
Upgrade available Upgrade to a release after 15.1
Interim mitigation

Disable or restrict access to the ELFinder connector at /vendor_extra/elfinder/ until a patch is applied; alternatively, upgrade to a patched Tiki Wiki version that enforces proper file type validation in the ELFinder component.

Recommended fix Moderate confidence

Tiki Wiki CMS Groupware version 22.x (latest stable release)

  1. 1. Backup your current Tiki Wiki CMS Groupware installation and database before making any changes.
  2. 2. Navigate to the official Tiki Wiki download page at https://tiki.org/download to obtain the latest stable version.
  3. 3. Download the most recent stable release (version 22 or later recommended).
  4. 4. Following Tiki Wiki's upgrade documentation, extract the new files to your web server, ensuring to preserve your local.php configuration file and any custom themes or templates.
  5. 5. Run the Tiki upgrade script by accessing your site, which will automatically migrate the database to the new version.
  6. 6. Verify that the /vendor_extra/elfinder/ directory has been updated or removed as part of the new installation.
  7. 7. After upgrade, confirm the ELFinder component now properly validates file types and restricts uploads to non-executable file types.
Caveat Major version upgrades in Tiki Wiki may introduce changes to plugin syntax, database schema, and theme rendering; review the release notes for any backward-incompatible changes before deploying to production.

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

Fix this in Tikiwiki Cms\/groupware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34111 — 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-34111 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