CVE-2007-5430 json
Multiple SQL injection vulnerabilities in Stride 1.0 allow remote attackers to execute arbitrary SQL commands via (1) the p parameter to ma…
published 2007-10-12 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5406
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 3
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Stride 1.0 allow remote attackers to execute arbitrary SQL commands via (1) the p parameter to main.php in the Content Management System, (2) the id parameter in a sto cmd action to shop.php in the Merchant subsystem, or the (3) course or (4) provider parameter to detail.php in the Courses subsystem.
Timeline
- First public exploit (EDB-30664)
- Published
Exploit prediction
1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-30664 Scott Manktelow Design Stride 1.0 - 'Merchant shop.php' SQL Injection webapps, 2007-10-11
- EDB-30662 Scott Manktelow Design Stride 1.0 - 'Content Management System main.php' SQL Injection webapps, 2007-10-11
- EDB-30660 Scott Manktelow Design Stride 1.0 Courses - 'detail.php' Multiple SQL Injections webapps, 2007-10-11
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
-
securityfocus.com
/bid/26036
vdb-entry
-
securityfocus.com
/archive/1/482006/100/0/threaded
mailing-list
-
securityfocus.com
/bid/26046
vdb-entry
-
securityreason.com
/securityalert/3216
third-party-advisory
-
securityfocus.com
/bid/26041
vdb-entry
-
osvdb.org
/43494
vdb-entry
- securityvulns.ru /Sdocument4.html
-
osvdb.org
/43491
vdb-entry
-
osvdb.org
/43492
vdb-entry
Sources
- CVE List CVE-2007-5430
- NVD CVE-2007-5430
Fencer Vulns 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.