Security readout for executives and security teams
Plain-English summary
CVE-2024-0610 affects a WordPress WooCommerce payment gateway plugin for Piraeus Bank. An unauthenticated attacker could abuse a payment reference field to query the site database. For an ecommerce site, this creates urgent risk to customer data, order records, credentials, and site availability.
Executive priority
Treat this as urgent for any affected ecommerce site. The vulnerability is unauthenticated, network reachable, and database-impacting. Prioritize inventory, update or disablement, and post-remediation review for possible data exposure.
Technical view
The issue is time-based blind SQL injection in the MerchantReference parameter of Piraeus Bank WooCommerce Payment Gateway versions up to and including 1.6.5.1. Sources attribute it to insufficient escaping and query preparation. CVSS 3.1 is 9.8 with network, unauthenticated, no-user-interaction attack conditions.
Likely exposure
Exposure is limited to WordPress sites running the affected WooCommerce payment gateway plugin, especially public checkout or payment callback paths. The source bundle does not identify other products or platforms as affected.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle. The sources describe unauthenticated SQL injection capability, but they do not provide evidence of active exploitation in the supplied material.
Researcher notes
The public description supports CWE-89 and time-based blind SQL injection via MerchantReference. Avoid assuming exploit-in-the-wild status from severity alone. The source bundle references a WordPress Trac changeset, but does not clearly state a fixed version number.
Mitigation direction
- Inventory WordPress sites for the Piraeus Bank WooCommerce Payment Gateway plugin.
- Update beyond version 1.6.5.1 if a vendor-fixed release is available.
- If no fixed release is available, disable the plugin pending vendor guidance.
- Review Wordfence and WordPress plugin guidance for confirmed remediation details.
- Back up and review ecommerce databases for suspicious access indicators.
Validation and detection
- Confirm installed plugin name and version on every WooCommerce site.
- Check whether public payment flows accept MerchantReference handling from unauthenticated users.
- Review web, WordPress, and database logs for anomalous SQL errors or delays.
- Verify the deployed plugin code includes the referenced WordPress Trac changeset.
- Confirm checkout and payment processing still work after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-0610 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f17c4748-2a95-495c-ad3b-86b272855791?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3035641%40woo-payment-gateway-for-piraeus-bank&new=3035641%40woo-payment-gateway-for-piraeus-bank&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.