CVE-2013-3631 json
NAS4Free 9.1.0.1.804 and earlier allows remote authenticated users to execute arbitrary PHP code via a request to exec.php, aka the "Advanc…
published 13y ago modified 4mo ago also EUVD-2013-3564
- cvss
- 6.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.7%
- EPSS 13.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
NAS4Free 9.1.0.1.804 and earlier allows remote authenticated users to execute arbitrary PHP code via a request to exec.php, aka the "Advanced | Execute Command" feature. NOTE: this issue might not be a vulnerability, since it appears to be part of legitimate, intentionally-exposed functionality by the developer and is allowed within the intended security policy.
Is CVE-2013-3631 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/nas4free_php_exec)
- Published
Exploit prediction
13.73% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/nas4free_php_exec NAS4Free Arbitrary Remote Code Execution metasploit exploit, great rank, 2013-10-30
- EDB-29320 NAS4Free - Remote 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 | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
community.rapid7.com
/community/metasploit/blog/2013/10/30/seven-tricks-and-treats
exploit
-
kb.cert.org
/vuls/id/326830
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2013-3631
- NVD CVE-2013-3631
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.