CVE-2010-0673 json
SQL injection vulnerability in cplphoto.php in the Copperleaf Photolog plugin 0.16, and possibly earlier, for WordPress allows remote attac…
published 16y ago modified 4mo ago also EUVD-2010-0701
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in cplphoto.php in the Copperleaf Photolog plugin 0.16, and possibly earlier, for WordPress allows remote attackers to execute arbitrary SQL commands via the postid parameter.
Is CVE-2010-0673 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 (EDB-11458)
- Published
Exploit prediction
2.82% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11458 WordPress Plugin Copperleaf Photolog 0.16 - SQL Injection webapps, 2010-02-15
- packetstormsecurity.org http://packetstormsecurity.org/1002-exploits/wpcopperleaf-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/38239 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
-
exploit-db.com
/exploits/11458
exploit
-
packetstormsecurity.org
/1002-exploits/wpcopperleaf-sql.txt
exploit
-
securityfocus.com
/bid/38239
vdb-entry, exploit
-
secunia.com
/advisories/38579
third-party-advisory, vendor-advisory
-
osvdb.org
/62346
vdb-entry
Sources
- CVE List CVE-2010-0673
- NVD CVE-2010-0673
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.