CVE-2009-4367 json
The Staging Webservice ("sitecore modules/staging/service/api.asmx") in Sitecore Staging Module 5.4.0 rev.080625 and earlier allows remote…
published 2009-12-21 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4335
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.1%
- EPSS 6.1% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
The Staging Webservice ("sitecore modules/staging/service/api.asmx") in Sitecore Staging Module 5.4.0 rev.080625 and earlier allows remote attackers to bypass authentication and (1) upload files, (2) download files, (3) list directories, and (4) clear the server cache via crafted SOAP requests with arbitrary Username and Password values, possibly related to a direct request.
Timeline
- First public exploit (EDB-10513)
- Published
Exploit prediction
6.09% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10513 Sitecore Staging Module 5.4.0 - Authentication Bypass / File Manipulation webapps, 2009-12-17
- sec-consult.com https://www.sec-consult.com/files/20091217-0_sitecore_StagingModule_1.0.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/37388 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
exploit-db.com
/exploits/10513
exploit
-
sec-consult.com
/files/20091217-0_sitecore_StagingModule_1.0.txt
exploit
-
securityfocus.com
/bid/37388
vdb-entry, exploit
-
secunia.com
/advisories/37763
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/508529/100/0/threaded
mailing-list
-
osvdb.org
/61147
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54881
vdb-entry
Sources
- CVE List CVE-2009-4367
- NVD CVE-2009-4367
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.