CVE-2021-28110
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 · unedited/exec in TranzWare e-Commerce Payment Gateway (TWEC PG) before 3.1.27.5 had a vulnerability in its XML parser.
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 · moderate confidenceThe /exec endpoint in TranzWare e-Commerce Payment Gateway before version 3.1.27.5 contains a vulnerability in its XML parser. The CVSS 7.5 score indicates a high-severity, likely remotely exploitable issue without authentication, affecting the server-side XML processing functionality of the payment gateway.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.1.27.5CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify the installed version of TranzWare e-Commerce Payment GatewayCheck the product version by querying the gateway's admin interface, inspecting the about/help page, or reviewing the installation manifest/version file shipped with the software. The version number is typically displayed in the gateway's web interface footer or in a versioninfo endpoint.Affected if The installed version is lower than 3.1.27.5 (e.g., 3.1.27.4, 3.1.26.x, or earlier)
-
Verify the /exec endpoint is accessibleAttempt to access the /exec endpoint on the server (e.g., GET https://your-gateway-host/exec or http://your-gateway-host:port/exec). If the endpoint responds (even with an error), it is exposed.Affected if The /exec endpoint returns any HTTP response, indicating it is exposed and accepting requests
-
Confirm XML processing is enabled on the /exec endpointSend a request to the /exec endpoint with an XML payload (e.g., a simple XML structure like <?xml version="1.0"?><test></test>) via POST. If the server processes the XML and returns a response rather than rejecting it, XML processing is active.Affected if The server accepts and processes XML payloads sent to /exec, returning a parsed response or XML-related error message
You are affected if your TranzWare e-Commerce Payment Gateway version is below 3.1.27.5 AND the /exec endpoint is exposed with XML processing enabled.
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 data3.1.27.5
Upgrade TranzWare e-Commerce Payment Gateway to version 3.1.27.5 or later to remediate this XML parser vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28110 — 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-2021-28110 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