dbcve.org
RuncommandApplication · Aelsantex

CVE-2025-51958

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-30
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 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
aelsantex runcommand 2014-04-01, a plugin for DokuWiki, allows unauthenticated attackers to execute arbitrary system commands via lib/plugins/runcommand/postaction.php.

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

A command injection vulnerability in the aelsantex runcommand DokuWiki plugin (2014-04-01) allows unauthenticated attackers to execute arbitrary system commands via the postaction.php file. The plugin appears to lack proper input sanitization on user-supplied parameters passed to system shell commands.

MitigationImmediately remove or disable the runcommand plugin if not essential. If required, implement strict input validation and parameterized commands to prevent command injection, or migrate to a maintained alternative.

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
RuncommandApplication
Affected:= 2014-04-01

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. Locate the runcommand plugin installation
    Check your DokuWiki plugins directory for a folder named 'runcommand', 'runcommand_aelsantex', or similar. Common paths include lib/plugins/ or /var/www/html/lib/plugins/
    Affected if The runcommand plugin folder exists in the DokuWiki installation
  2. Verify the plugin version
    Inspect the plugin's plugin.info.txt file or main PHP file to determine the version number. Look for a version string or date stamp.
    Affected if The installed version is exactly 2014-04-01 or cannot be determined (assumed vulnerable)
  3. Check for the vulnerable postaction.php file
    Look for a file named postaction.php within the runcommand plugin directory. This is the specific file that handles the vulnerable request handling.
    Affected if The postaction.php file exists in the plugin directory
  4. Confirm plugin is enabled
    Check your DokuWiki configuration (conf/plugins.php or the plugin manager interface) to see if the runcommand plugin is listed as active or enabled.
    Affected if The plugin is enabled and loaded by DokuWiki

A DokuWiki installation is affected if it has the runcommand plugin (version 2014-04-01) installed with postaction.php present and the plugin is enabled.

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

Immediately remove or disable the runcommand plugin if not essential. If required, implement strict input validation and parameterized commands to prevent command injection, or migrate to a maintained alternative.

Recommended fix High confidence
  1. 1. Identify if the runcommand plugin is installed on the DokuWiki instance
  2. 2. Remove the entire runcommand plugin directory (lib/plugins/runcommand/) from the DokuWiki installation
  3. 3. If the functionality is needed, implement an alternative secure solution that does not involve executing system commands from the web application
  4. 4. Audit the server for any signs of compromise since the vulnerability allows unauthenticated remote code execution
  5. 5. Consider migrating to a newer DokuWiki version that does not include deprecated plugins
Caveat The runcommand plugin was deprecated and removed from the DokuWiki plugin repository due to inherent security risks; there is no safe version to upgrade to - the plugin must be removed entirely

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

Fix this in Runcommand Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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