CVE-2026-5344
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 security vulnerability has been detected in Textpattern up to 4.9.1. Affected by this vulnerability is the function mt_uploadImage of the file rpc/TXP_RPCServer.php of the component XML-RPC Handler. The manipulation of the argument file.name leads to path traversal. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor confirmed the issue and will provide a fix in the upcoming release.
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 confidencePath traversal vulnerability in Textpattern CMS XML-RPC handler where the mt_uploadImage function fails to sanitize the file.name parameter, allowing attackers to manipulate file paths and write files outside the intended upload directory.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify Textpattern installation and versionLocate the Textpattern installation directory and check the version file (typically version.php or composer.json in the root directory). Run: find /var/www -name 'version.php' -path '*/textpattern/*' 2>/dev/null && cat /path/to/textpattern/version.phpAffected if Textpattern version is present and matches the affected version range for this CVE (check against known vulnerable versions)
-
Verify XML-RPC API endpoint is accessibleCheck if the XML-RPC endpoint exists and is accessible. The vulnerable file is rpc/TXP_RPCServer.php. Run: curl -X POST http://TARGET_HOST/textpattern/rpc/TXP_RPCServer.php -d '<?xml version="1.0"?><methodCall><methodName>mt.uploadImage</methodName></methodCall>'Affected if HTTP response returns XML content (indicates XML-RPC is enabled and responding)
-
Confirm XML-RPC is enabled in configurationCheck Textpattern configuration file (config.php) for XML-RPC settings. Run: grep -i 'xmlrpc' /path/to/textpattern/config.phpAffected if XML-RPC is not explicitly disabled or the endpoint responds to requests (default configuration allows it)
-
Check file upload permissions and pathsReview the preferences for file uploads in the admin panel or database. Check for $this->prefs['file_max_upload_size'] and upload path settings in the database: SELECT name,val FROM txp_prefs WHERE name LIKE '%file%'Affected if File uploads are enabled and a custom upload path is configured (vulnerability allows escaping the intended upload directory)
A user is affected if they run a vulnerable Textpattern version with XML-RPC API enabled and accessible, allowing unauthenticated attackers to manipulate file.name parameters for path traversal during image uploads.
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 dataDisable the XML-RPC handler if unused; implement WAF rules to block path traversal patterns in upload parameters until the vendor patch is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5344 — 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-2026-5344 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