The IVPAY payments WordPress plugin through 1.0.8 does not sanitise a value from its payment callback before using it in a SQL statement, and treats an empty API key, which is its own default, as valid authentication, allowing unauthenticated attackers to read arbitrary data from the database.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Thu, 05 Nov 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-89 |
Thu, 05 Nov 2026 06:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The IVPAY payments WordPress plugin through 1.0.8 does not sanitise a value from its payment callback before using it in a SQL statement, and treats an empty API key, which is its own default, as valid authentication, allowing unauthenticated attackers to read arbitrary data from the database. | |
| Title | IVPAY payments <= 1.0.8 - Unauthenticated SQLi via 'payment_id' Parameter | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-11-05T06:00:28.484Z
Reserved: 2026-09-25T11:35:01.266Z
Link: CVE-2026-100144
No data.
Status : Received
Published: 2026-11-05T06:17:06.640
Modified: 2026-11-05T06:17:06.640
Link: CVE-2026-100144
No data.
OpenCVE Enrichment
Updated: 2026-11-05T07:30:14Z
Weaknesses