CVE-2013-3629 in the critical feed json
ISPConfig 3.0.5.2 has Arbitrary PHP Code Execution
published 6y ago modified 4mo ago also EUVD-2013-3563
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 43.1%
- EPSS 43.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
ISPConfig 3.0.5.2 has Arbitrary PHP Code Execution
Is CVE-2013-3629 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/multi/http/ispconfig_php_exec)
- Published
Exploit prediction
43.10% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/ispconfig_php_exec ISPConfig Authenticated Arbitrary PHP Code Execution metasploit exploit, excellent rank, 2013-10-30
- EDB-29322 ISPConfig - (Authenticated) Arbitrary PHP Code Execution (Metasploit) remote, 2013-10-31
- community.rapid7.com https://community.rapid7.com/community/metasploit/blog/2013/10/30/seven-tricks-and-treats referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- ISPConfig ISPConfig
References
-
community.rapid7.com
/community/metasploit/blog/2013/10/30/seven-tricks-and-treats
exploit, third-party-advisory
-
exploit-db.com
/exploits/29322
exploit, third-party-advisory, vdb-entry
-
community.rapid7.com
/community/metasploit/blog/2013/10/30/seven-foss-disclosures-part-one
third-party-advisory
-
securityfocus.com
/bid/63455
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2013-3629
- NVD CVE-2013-3629
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.