CVE-2022-1692 in the critical feed json
CP Image Store with Slideshow < 1.0.68 - Unauthenticated SQLi
published 4y ago modified 4mo ago also EUVD-2022-24977
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.4%
- EPSS 10.4% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The CP Image Store with Slideshow WordPress plugin before 1.0.68 does not sanitise and escape the ordering_by query parameter before using it in a SQL statement in pages where the [codepeople-image-store] is embed, allowing unauthenticated users to perform an SQL injection attack
Patch / fix
- dwbooster cp_image_store_with_slideshow 1.0.68
Is CVE-2022-1692 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
10.38% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template CP Image Store with Slideshow <= 1.0.67 - SQL Injection nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/83bae80c-f583-4d89-8282-e6384bbc7571 referenced PoC, tagged "exploit" by a source, unverified
- bulletin.iese.de https://bulletin.iese.de/post/cp-image-store_1-0-67 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Unknown CP Image Store with Slideshow
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wpscan.com
/vulnerability/83bae80c-f583-4d89-8282-e6384bbc7571
exploit, third-party-advisory
-
bulletin.iese.de
/post/cp-image-store_1-0-67
exploit, third-party-advisory
Sources
- CVE List CVE-2022-1692
- NVD CVE-2022-1692
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.