CVE-2015-1875
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier...
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier allows remote attackers to execute arbitrary SQL commands via the transactionID parameter.
Exploit likelihood
What each source reports
NVD Score used
7.5
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier allows remote attackers to execute arbitrary SQL commands via the transactionID parameter.
- Record
CVE-2015-1875- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-89
- Updated
- 2026-11-02
CVE List No score
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier allows remote attackers to execute arbitrary SQL commands via the transactionID parameter.
- Record
CVE-2015-1875- Updated
- 2026-11-02
EUVDEUVD-2015-1981 No score
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier allows remote attackers to execute arbitrary SQL commands via the transactionID parameter.
- Record
EUVD-2015-1981- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-979w-5pw3-m5wg No score
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier...
SQL injection vulnerability in a2billing/customer/iridium_threed.php in Elastix 2.5.0 and earlier allows remote attackers to execute arbitrary SQL commands via the transactionID parameter.
- Record
GHSA-979w-5pw3-m5wg- Weakness
- CWE-89
- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | Elastix 2.x - Blind SQL Injection | 2015-03-07 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2015-1875 is a high vulnerability (CVSS 7.5) in Palosanto Elastix, published March 11, 2015. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 1.27%, the 69th percentile. No source names a fixed version.