CVE-2015-3173 json
custom-content-type-manager Wordpress plugin can be used by an administrator to achieve arbitrary PHP remote code execution.
published 4y ago modified 4mo ago also EUVD-2015-3250
- cvss
- 7.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
custom-content-type-manager Wordpress plugin can be used by an administrator to achieve arbitrary PHP remote code execution.
Patch / fix
- custom_content_type_manager_project custom_content_type_manager 0.9.8.6
Is CVE-2015-3173 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 FencerExploit prediction
3.32% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/6b3d0736-7f08-4403-95eb-4385cb206f9e referenced PoC, tagged "exploit" by a source, unverified
- blog.nettitude.com https://blog.nettitude.com/uk/custom-content-type-manager-remote-code-execution referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/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
- n/a custom-content-type-manager
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
-
wpscan.com
/vulnerability/6b3d0736-7f08-4403-95eb-4385cb206f9e
exploit, third-party-advisory
-
blog.nettitude.com
/uk/custom-content-type-manager-remote-code-execution
exploit, third-party-advisory
-
github.com
/craftsmancoding/custom-content-type-manager/blob/master/readme.txt
release-notes, third-party-advisory
Sources
- CVE List CVE-2015-3173
- NVD CVE-2015-3173
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.