CVE-2019-25075
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 · uneditedHTML injection combined with path traversal in the Email service in Gravitee API Management before 1.25.3 allows anonymous users to read arbitrary files via a /management/users/register request.
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 confidenceHTML injection combined with path traversal in Gravitee API Management's Email service before version 1.25.3 allows unauthenticated attackers to read arbitrary files on the server via the /management/users/register endpoint. The vulnerability stems from insufficient input validation on user registration parameters.
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< 1.25.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Gravitee API Management presenceIdentify if Gravitee APIM is deployed in your environment by checking for the gravitee process, web application, or Docker containerAffected if Gravitee API Management is not installed in your environment (not affected)
-
Determine installed versionLocate the Gravitee APIM version from startup logs, the management console (typically at /management/#/about), or the configuration files. Compare your version against the affected range of < 1.25.3Affected if Your installed version is earlier than 1.25.3 and the Email service is enabled
-
Verify Email service is enabledCheck the Gravitee configuration (typically in the gravitee.yml or via the management API) to confirm whether the Email service/plugin is enabledAffected if The Email service is enabled in your Gravitee APIM instance
-
Check register endpoint accessibilityVerify whether the /management/users/register endpoint is exposed and reachable (network access, firewall rules, or proxy configuration)Affected if The endpoint is accessible from an untrusted network without authentication
You are affected if Gravitee API Management version is earlier than 1.25.3, the Email service is enabled, and the /management/users/register endpoint is accessible to untrusted users.
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.
dbcve · scoped1.25.3
Upgrade Gravitee API Management to version 1.25.3 or later. Until upgrade is possible, restrict access to the /management/users/register endpoint and implement strict input validation to prevent path traversal sequences.
1.25.3 or later
- 1. Identify the current Gravitee API Management version in use
- 2. Backup the current installation and configuration
- 3. Upgrade Gravitee API Management to version 1.25.3 or later
- 4. Verify the upgrade was successful and the service is operational
- 5. Test the /management/users/register endpoint to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25075 — 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-2019-25075 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