CVE-2024-48346
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 · uneditedxtreme1 <= v0.9.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the /api/data/upload path. The vulnerability is triggered through the fileUrl parameter, which allows an attacker to make arbitrary requests to internal or external systems.
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 confidencextreme1 versions up to and including v0.9.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the /api/data/upload endpoint. The fileUrl parameter is not properly validated, allowing an attacker to manipulate the server into making arbitrary HTTP requests to internal or external systems, potentially exposing internal services and infrastructure.
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
- 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 xtreme1 installation and versionLocate the xtreme1 application and check its version file (such as version info in the application metadata, pom.xml, or version displayed in the application UI/headers). Compare the installed version to v0.9.1 or earlier.Affected if The installed version is xtreme1 v0.9.1 or any earlier version.
-
Identify if the /api/data/upload endpoint existsReview application routing configuration, API documentation, or scan for the /api/data/upload endpoint path in the deployed application.Affected if The /api/data/upload endpoint is present and exposed in the application.
-
Verify the fileUrl parameter is acceptedSend a test request to the /api/data/upload endpoint with a fileUrl parameter (e.g., fileUrl=http://example.com) and observe if the parameter is processed without validation errors.Affected if The endpoint accepts and processes the fileUrl parameter without rejecting arbitrary URLs.
-
Check if network restrictions are disabledExamine application configuration files or security settings for any URL validation, allowlisting, or RFC 1918/localhost request blocking mechanisms related to the upload functionality.Affected if No URL validation, domain allowlisting, or internal network request blocking is configured for the fileUrl parameter.
You are affected if xtreme1 v0.9.1 or earlier is installed, the /api/data/upload endpoint is accessible, the fileUrl parameter is processed, and no URL validation or network restrictions are configured.
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 dataImplement strict input validation and URL allowlisting for the fileUrl parameter to restrict requests to approved domains or IP ranges. Additionally, disable or restrict the ability to make requests to internal network addresses (RFC 1918) and localhost.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48346 — 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-2024-48346 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