dbcve.org
SparkshopApplication

CVE-2024-48107

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to after 1.1.7 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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
SparkShop <=1.1.7 is vulnerable to server-side request forgery (SSRF). This vulnerability allows attacks to scan ports on the Intranet or local network where the server resides, attack applications running on the Intranet or local network, or read metadata on the cloud server.

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 confidence

SparkShop versions 1.1.7 and below contain a server-side request forgery (SSRF) vulnerability. Attackers can abuse this flaw to make the server perform requests to arbitrary internal or external resources, enabling port scanning of intranet/local network hosts, attacks against internal applications, and retrieval of cloud metadata services.

MitigationImplement strict input validation with allowlist-based filtering for URL/hostname inputs, restrict outbound requests to permitted destinations, and disable access to cloud metadata endpoints (e.g., 169.254.169.254).

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
SparkshopApplication
Affected:<= 1.1.7

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SparkShop version
    Locate the version file or configuration in your SparkShop installation (commonly found in version files, composer.json, or admin panel about page) and note the exact version number
    Affected if The installed version is 1.1.7 or any lower version (e.g., 1.1.6, 1.1.5, etc.)
  2. Locate URL/hostname input functionality
    Search your codebase for endpoints, controllers, or functions that accept URL or hostname parameters from user input - look for features like URL validators, link checkers, webhook configurators, or external resource fetchers
    Affected if Your installation has any feature that accepts and processes user-supplied URLs or hostnames
  3. Identify SSRF-vulnerable endpoint
    Review request handling code for functions that make outbound HTTP requests (using functions like file_get_contents, curl, Guzzle, etc.) with user-controlled URL parameters
    Affected if There exists an endpoint that uses user input to construct outbound HTTP requests without proper validation
  4. Check network configuration
    Examine your server and application firewall rules, network policies, and cloud security groups for egress filtering
    Affected if Outbound network requests from the application server are not restricted to an allowlist of permitted destinations
  5. Verify cloud metadata access
    Check if your cloud environment (AWS, Azure, GCP, etc.) has metadata endpoints accessible from the SparkShop server (typically at 169.254.169.254)
    Affected if Cloud metadata services are reachable from the application server without restrictions

You are affected if your SparkShop version is 1.1.7 or lower AND your installation includes any feature that accepts user-supplied URLs or hostnames for making outbound requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.1.7
Interim mitigation

Implement strict input validation with allowlist-based filtering for URL/hostname inputs, restrict outbound requests to permitted destinations, and disable access to cloud metadata endpoints (e.g., 169.254.169.254).

Fix this in Sparkshop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48107 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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