CVE-2025-50847
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 · uneditedCross Site Request Forgery (CSRF) vulnerability in CS Cart 4.18.3, allows attackers to add products to a user's comparison list via a crafted HTTP 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 confidenceCSRF vulnerability in CS Cart 4.18.3 allows unauthenticated attackers to trick authenticated users into adding products to their comparison list via crafted HTTP requests. The application lacks proper anti-CSRF token validation on the comparison list functionality, enabling cross-site request forgery attacks.
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= 4.18.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify the installed CS-Cart versionAccess the admin panel and navigate to Settings > General or check the app version file in the installation directory. Alternatively, inspect the HTTP headers or the changelog file included with the installation.Affected if The installed version is exactly 4.18.3
-
Confirm the comparison list feature is enabledLog into the CS-Cart admin panel and navigate to Settings > Comparison settings or check the comparison_list setting in the database configuration table. The feature is typically enabled by default.Affected if The comparison list feature is active in the storefront and accessible to customers
-
Inspect the comparison list request handler for CSRF protectionExamine the PHP controller handling the comparison list add/remove actions, typically located in the app/addons/comparison_list directory or the corresponding AJAX endpoint. Look for validation of anti-CSRF tokens in the request processing logic.Affected if The code handling comparison list modifications does not validate anti-CSRF tokens before processing state-changing requests
-
Verify Origin or Referer header validationReview the application-level request validation in the core dispatcher or the comparison list AJAX handler to determine if Origin or Referer HTTP headers are validated to prevent cross-origin requests.Affected if The application does not validate Origin or Referer headers on comparison list requests, allowing cross-origin forged requests
-
Test the comparison list for CSRF vulnerabilityWith a browser that has an active authenticated session, submit a crafted POST request to the comparison list endpoint from a different origin (or use a tool like Burp Suite to remove anti-CSRF tokens) and observe if the product is added to the comparison list without token validation.Affected if The comparison list accepts and processes requests without valid anti-CSRF tokens, confirming the CSRF protection is absent
A user is affected if their CS-Cart installation is version 4.18.3 AND the comparison list feature is enabled AND the application lacks anti-CSRF token validation on comparison list requests.
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 anti-CSRF tokens (synchronizer token pattern) on all state-changing requests including the comparison list feature, and validate Origin/Referer headers to prevent cross-origin forged requests.
- 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-2025-50847 — 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-2025-50847 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