dbcve.org
LikeshopApplication

CVE-2024-24028

MEDIUM · 5.9 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 2.5.7 or later.
See remediation →
64/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
Server Side Request Forgery (SSRF) vulnerability in Likeshop before 2.5.7 allows attackers to view sensitive information via the avatar parameter in function UserLogic::updateWechatInfo.

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in Likeshop before version 2.5.7 in the UserLogic::updateWechatInfo function. The avatar parameter accepts user-supplied URLs without proper validation, allowing attackers to make the server perform arbitrary requests to internal or external resources, potentially exposing sensitive information.

MitigationUpgrade to Likeshop version 2.5.7 or later. Additionally, implement strict URL validation and allowlist controls for the avatar parameter to prevent arbitrary URL injection.

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
LikeshopApplication
Affected:< 2.5.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 Likeshop installation and version
    Locate the Likeshop installation directory or check the application version file (commonly version.php, composer.json, or similar version metadata file depending on installation method). Compare the installed version number to the affected range (< 2.5.7).
    Affected if The installed version is below 2.5.7
  2. Locate the UserLogic class file
    Search for the UserLogic.php file within the application source code, typically found under the application logic or library directory. Verify the updateWechatInfo method exists in this file.
    Affected if The UserLogic::updateWechatInfo function exists in the codebase and the application version is vulnerable
  3. Verify avatar parameter handling in updateWechatInfo
    Examine the updateWechatInfo function code in UserLogic.php. Look for the avatar parameter processing logic to confirm it accepts and processes user-supplied URL input without proper validation or allowlisting.
    Affected if The avatar parameter accepts arbitrary URLs without validation or allowlist checks
  4. Check API endpoint exposure
    Identify the API route or controller that calls UserLogic::updateWechatInfo. Determine if this endpoint is accessible (authenticated or unauthenticated) to external users.
    Affected if The updateWechatInfo function can be invoked via an accessible API endpoint with user-controlled avatar parameter

The environment is affected if Likeshop version is below 2.5.7 and the UserLogic::updateWechatInfo function with the vulnerable avatar parameter is accessible and processes user-supplied URLs without validation.

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.

dbcve · scoped
Upgrade available Upgrade to 2.5.7 or later
Fixed in 2.5.7
Interim mitigation

Upgrade to Likeshop version 2.5.7 or later. Additionally, implement strict URL validation and allowlist controls for the avatar parameter to prevent arbitrary URL injection.

Recommended fix Moderate confidence

2.5.7

  1. Back up the current Likeshop installation and database before proceeding with the upgrade
  2. Upgrade Likeshop to version 2.5.7 by downloading the latest release from the official repository or package manager
  3. After upgrading, verify that the UserLogic::updateWechatInfo function now properly validates and sanitizes the avatar parameter to prevent SSRF attacks
  4. Test the user profile update functionality to ensure the fix works correctly
  5. Monitor server logs for any attempted SSRF requests to confirm the vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Likeshop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24028 — 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-24028 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