Skip to content
Noroxi
CVE-2009-2265· NVD / CVE Program· CNA mitre

Multiple directory traversal vulnerabilities in FCKeditor before 2.6.4.1 allow remote attackers to create executable files in arbitrary dire

Multiple directory traversal vulnerabilities in FCKeditor before 2.6.4.1 allow remote attackers to create executable files in arbitrary directories via directory traversal sequences in the input to unspecified connector modules, as exploited in the wild for remote code execution in July 2009, related to the file browser and the editor/filemanager/connectors/ directory.

HighCVSS 7.5 · v2.0—Weaponized Fix available
Published
Jul 5, 2009
Updated
Jun 16, 2026
EPSS
83.7% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

55

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
25 / 30 · 83.7%

Affected systems

VendorProduct
fckeditorfckeditor

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fckeditor fckeditorup to 2.6.4 inclusive
  • fckeditor fckeditor2.0
  • fckeditor fckeditor2.0_fc
  • fckeditor fckeditor2.0_rc2
  • fckeditor fckeditor2.0rc2
  • fckeditor fckeditor2.0rc3
  • fckeditor fckeditor2.1
  • fckeditor fckeditor2.1.1
  • fckeditor fckeditor2.2
  • fckeditor fckeditor2.3
  • fckeditor fckeditor2.3.1
  • fckeditor fckeditor2.3.2
  • fckeditor fckeditor2.3.3
  • fckeditor fckeditor2.4
  • fckeditor fckeditor2.4.1
  • fckeditor fckeditor2.4.2
  • fckeditor fckeditor2.4.3
  • fckeditor fckeditor2.5
  • fckeditor fckeditor2.5.1
  • fckeditor fckeditor2.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:5.0fckeditorbefore 1:2.6.2-1lenny11:2.6.2-1lenny1

Other highest-scoring records for the same primary product.

  • CVE-2008-6178Unrestricted file upload vulnerability in editor/filemanager/browser/default/connectors/php/connector.php in FCKeditor 2.2, as used in Falt4
    32Monitor
  • CVE-2006-0921Multiple directory traversal vulnerabilities in connector.php in FCKeditor 2.0 FC, as used in products such as RunCMS, allow remote attacker
    26Monitor
  • CVE-2006-0658Incomplete blacklist vulnerability in connector.php in FCKeditor 2.0 and 2.2, as used in products such as RunCMS, allows remote attackers to
    22Monitor
  • CVE-2006-2529editor/filemanager/upload/php/upload.php in FCKeditor before 2.3 Beta, when the upload feature is enabled, does not verify the Type paramete
    21Monitor
  • CVE-2005-0613Unknown vulnerability in FCKeditor 2.0 RC2, when used with PHP-Nuke, allows remote attackers to upload arbitrary files.
    21Monitor
  • CVE-2009-2324Multiple cross-site scripting (XSS) vulnerabilities in FCKeditor before 2.6.4.1 allow remote attackers to inject arbitrary web script or HTM
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:fckeditor1:2.6.2-1lenny1 · Debian:5.0Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Exploit-DB entry ×2
  • Proof-of-concept repository on GitHub ×7

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2021-06-24
Exploit-DB entrywebapps2010-11-24
Metasploit moduleexploit/windows/http/coldfusion_fckeditorColdFusion 8.0.1 Arbitrary File Upload and Executeexploit2009-07-03
Proof-of-concept repository on GitHubstars:22020-10-02
Proof-of-concept repository on GitHubstars:12021-07-15
Proof-of-concept repository on GitHubstars:12022-01-14
Proof-of-concept repository on GitHubstars:12024-12-18
Proof-of-concept repository on GitHubstars:02025-09-27
Proof-of-concept repository on GitHubstars:02026-01-12
Proof-of-concept repository on GitHubstars:02026-09-15

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-3 d
  2. Published
  3. First PoC+506 d
  4. TodaySep 30, 2026+6296 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
P · data or configuration can be modified
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
P
Integrity impact
P
Availability impact
P

CVSS vector

AV:N/AC:L/Au:N/C:P/I:P/A:P

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records