CVE-2025-28942
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Trust Payments Trust Payments Gateway for WooCommerce trust-payments-hosted-payment-pages-integration allows SQL Injection.This issue affects Trust Payments Gateway for WooCommerce: from n/a through <= 1.1.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the Trust Payments Gateway for WooCommerce plugin (trust-payments-hosted-payment-pages-integration) allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling unauthorized database access, data exfiltration, or data manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin presenceIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Trust Payments Gateway for WooCommerce' or 'trust-payments-hosted-payment-pages-integration'Affected if The plugin is installed and active in WooCommerce
-
Determine installed versionClick on the plugin to view version details, or inspect the main plugin PHP file header in wp-content/plugins/trust-payments-hosted-payment-pages-integration/Affected if The installed version is not the latest patched release
-
Identify exposed payment endpointsReview WooCommerce settings under Payments or Trust Payments configuration. Identify any endpoints handling user-supplied input such as transaction IDs, customer references, or payment response parametersAffected if Plugin processes external input through payment-related functions without documented sanitization
-
Examine plugin file for input handlingInspect the main plugin PHP files for $_GET, $_POST, or $_REQUEST usage around SQL queries. Look for database calls that incorporate unsanitized variablesAffected if Code contains direct SQL queries using request parameters without prepared statements or escaping
-
Analyze web server logs for exploitation attemptsSearch access logs for requests to plugin endpoints containing SQL meta-characters (', ;, --, UNION, SELECT, OR 1=1) in query string parametersAffected if Suspicious SQL injection patterns appear in requests to the payment gateway
The environment is affected if the Trust Payments Gateway for WooCommerce plugin is installed and handles payment input without confirmed patched version status.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest patched version of the Trust Payments Gateway for WooCommerce plugin immediately; if no patched version is available, disable the plugin and consider taking the payment functionality offline until a fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data