CVE-2011-0407 json
SQL injection vulnerability in the store function in _phenotype/system/class/PhenoTypeDataObject.class.php in Phenotype CMS 3.0 allows remo…
published 2011-01-11 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0433
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 67%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the store function in _phenotype/system/class/PhenoTypeDataObject.class.php in Phenotype CMS 3.0 allows remote attackers to execute arbitrary SQL commands via a crafted URI, as demonstrated by Gallery/gal_id/1/image1,1.html. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-15922)
- Published
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15922 Phenotype CMS 3.0 - SQL Injection webapps, 2011-01-06
- htbridge.ch http://www.htbridge.ch/advisory/sql_injection_in_phenotype_cms.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/45700 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
htbridge.ch
/advisory/sql_injection_in_phenotype_cms.html
exploit
-
securityfocus.com
/bid/45700
vdb-entry, exploit
-
secunia.com
/advisories/42837
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64538
vdb-entry
-
securityfocus.com
/archive/1/515577/100/0/threaded
mailing-list
-
osvdb.org
/70308
vdb-entry
Sources
- CVE List CVE-2011-0407
- NVD CVE-2011-0407
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.