Skip to main content
VulnerabilityPublished Updated

CVE-2026-34414: thexerteproject xerteonlinetoolkits · Path Traversal

Affects thexerteproject xerteonlinetoolkitsSource CVE Database V5

0
Compare

Public exploit available (Metasploit) · CVSS 7.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.8% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    1 Metasploit module

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
thexerteprojectxerteonlinetoolkitsAffected
  • <=3.15.0
Fixed in–
GitHubthexerteproject/xerteonlinetoolkitspkg:github/thexerteproject/xerteonlinetoolkitsOther threatsAffected
  • <=3.15
Fixed in–
GitHubxerteonlinetoolkitspkg:github/xerteonlinetoolkitsOther threatsAffected
  • <=3.15.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, restrict access to the vulnerable endpoint and monitor for suspicious file operations. Avoid exposing the elFinder connector endpoint to untrusted users.

Description

Xerte Online Toolkits versions 3.15 and earlier contain a relative path traversal vulnerability in the elFinder connector endpoint at /editor/elfinder/php/connector.php where the name parameter in rename commands is not sanitized for path traversal sequences. Attackers can supply a name value containing directory traversal sequences to move files from project media directories to arbitrary locations on the filesystem, potentially overwriting application files, achieving stored cross-site scripting, or combining with other vulnerabilities to achieve unauthenticated remote code execution by moving PHP code files to the application root.

References

Community reviews

Loading reviews…