CVE-2025-13786
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 · uneditedA vulnerability was detected in taosir WTCMS up to 01a5f68a3dfc2fdddb44eed967bb2d4f60487665. Impacted is the function fetch of the file /index.php. Performing manipulation of the argument content results in code injection. It is possible to initiate the attack remotely. The exploit is now public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceCode injection vulnerability in WTCMS /index.php where the fetch function processes the 'content' parameter unsafely, likely through dynamic code execution (eval, system, or similar), allowing remote attackers to inject and execute arbitrary OS commands.
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<= 2019-12-20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Wtcms installationLocate the Wtcms installation by searching for the file /index.php and checking for Wtcms-specific directories (such as /app, /core, /runtime). Check for files containing 'Wtcms', 'wtcms', or 'WTCMS' in headers or comments.Affected if Wtcms is present on the system and the version cannot be determined or is <= 2019-12-20
-
Identify Wtcms versionSearch the codebase for version strings in files like /index.php, /config.php, /application/config.php, /version.php, or readme files. Compare the discovered version to the affected range (<= 2019-12-20).Affected if The installed version is 2019-12-20 or earlier, or no version information is found but the code appears old
-
Locate the fetch function in /index.phpOpen /index.php and search for the function definition 'function fetch' or 'public function fetch'. Identify how this function processes the 'content' parameter.Affected if A fetch function exists in /index.php that accepts a 'content' parameter
-
Detect unsafe dynamic code executionIn /index.php within the fetch function, search for dangerous PHP functions such as eval(), system(), exec(), shell_exec(), passthru(), or backticks (`) being used to process the 'content' parameter.Affected if The 'content' parameter is passed directly to eval() or a shell-execution function without sanitization
-
Test accessibility of the vulnerable parameterReview how user input reaches the fetch function. Check if the 'content' parameter can be supplied via HTTP request (GET/POST) to /index.php. Look for routes or entry points that pass user input to the fetch function.Affected if The 'content' parameter is user-controllable via HTTP requests to /index.php and reaches the unsafe code path
A system is affected if Wtcms version <= 2019-12-20 is installed and the fetch function in /index.php processes the 'content' parameter through eval() or a shell-execution function without sanitization.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict input validation and sanitization on all user-supplied parameters; replace unsafe dynamic code execution with parameterized functions; deploy a WAF as a temporary compensating control until the code is fixed.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13786 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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