How severe is CVE-2019-14277?

CVE-2019-14277 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-14277 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 7% (94th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-14277?

CVE-2019-14277 primarily affects Axway Securetransport. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-14277?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2019-14277 published?

CVE-2019-14277 was published on 2019-07-26 and last updated on 2026-06-17.

CVE-2019-14277

CVE-2019-14277 is a critical-severity vulnerability in Axway Securetransport with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-91.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 7% (94th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-91
Affected product: Axway Securetransport
Published: 2019-07-26
Last modified: 2026-06-17

Description

Axway SecureTransport 5.x through 5.3 (or 5.x through 5.5 with certain API configuration) is vulnerable to unauthenticated blind XML injection (and XXE) in the resetPassword functionality via the REST API. This vulnerability can lead to local file disclosure, DoS, or URI invocation attacks (i.e., SSRF with resultant remote code execution). NOTE: The vendor disputes this issues as not being a vulnerability because “All attacks that use external entities are blocked (no external DTD or file inclusions, no SSRF). The impact on confidentiality, integrity and availability is not proved on any version.

Frequently asked questions

What is CVE-2019-14277?: Axway SecureTransport 5.x through 5.3 (or 5.x through 5.5 with certain API configuration) is vulnerable to unauthenticated blind XML injection (and XXE) in the resetPassword functionality via the REST API. This vulnerability can lead to local file disclosure, DoS, or URI invocation attacks (i.e., SSRF with resultant remote code execution). NOTE: The vendor disputes this issues as not being a vulnerability because “All attacks that use external entities are blocked (no external DTD or file inclusions, no SSRF). The impact on confidentiality, integrity and availability is not proved on any version.
How severe is CVE-2019-14277?: CVE-2019-14277 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-14277 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 7% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-14277?: CVE-2019-14277 primarily affects Axway Securetransport. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-14277?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-14277 published?: CVE-2019-14277 was published on 2019-07-26 and last updated on 2026-06-17.

References

Affected products (5)

cpe:2.3:a:axway:securetransport:5.2.1:*:*:*:*:*:*:*
cpe:2.3:a:axway:securetransport:5.3.0:*:*:*:*:*:*:*
cpe:2.3:a:axway:securetransport:5.3.1:*:*:*:*:*:*:*
cpe:2.3:a:axway:securetransport:5.3.3:*:*:*:*:*:*:*
cpe:2.3:a:axway:securetransport:5.3.6:*:*:*:*:*:*:*

More vulnerabilities in Axway Securetransport

CVE-2012-4991 — High (CVSS 8.5): Multiple directory traversal vulnerabilities in Axway SecureTransport 5.1 SP2 and earlier allow remote authenticated…
CVE-2013-7057 — Medium (CVSS 6.8): Cross-site request forgery (CSRF) vulnerability in Axway SecureTransport 5.1 SP2 and earlier allows remote attackers to…

All CVEs affecting Axway Securetransport →

Other CWE-91 (XML Injection) vulnerabilities

CVE-2021-4140 — Critical (CVSS 10.0): It was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox. This vulnerability…
CVE-2023-43187 — Critical (CVSS 9.8): A remote code execution (RCE) vulnerability in the xmlrpc.php endpoint of NodeBB Inc NodeBB forum software prior to…
CVE-2019-19450 — Critical (CVSS 9.8): paraparser in ReportLab before 3.5.31 allows remote code execution because start_unichar in paraparser.py evaluates…
CVE-2021-37154 — Critical (CVSS 9.8): In ForgeRock Access Management (AM) before 7.0.2, the SAML2 implementation allows XML injection, potentially enabling a…
CVE-2020-29128 — Critical (CVSS 9.8): petl before 1.68, in some configurations, allows resolution of entities in an XML document.
CVE-2020-25216 — Critical (CVSS 9.8): yWorks yEd Desktop before 3.20.1 allows code execution via an XSL Transformation when using an XML file in conjunction…

Browse all CWE-91 (XML Injection) vulnerabilities →