sales@hackhalt.com

Home / Threats / CVE-2026-100144

IVPAY payments - Security Vulnerability (CVE-2026-100144)

CVE-2026-100144

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.

CVE-2026-100144

CRITICAL CVSS 9.3 Published 2026-11-05 Updated 2026-11-06
AI Risk Critical (92/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate
Severity Band CRITICAL
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Critical (92/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-05 CVE published and first recorded in the threat feed.
  2. 2026-11-06 Record updated with latest vulnerability metadata.
  3. 2026-11-12 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 16 hours ago

AI enriched 16 hours ago (2026-11-12 02:30 UTC)

Technical Summary

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.

Potential Impact

Severity is CRITICAL (CVSS 9.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 92/100 (Critical, High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

IVPAY payments PLUGIN · ivpay-payments Affected range not specified Fixed version not specified

References

What to do about this

Patch immediately Serious, and reachable without meaningful privilege.

Fix it

Update IVPAY payments to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs IVPAY payments, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs IVPAY payments. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update IVPAY payments to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.