CVE-2025-50849: CS Cart 4.18.3 is vulnerable to Insecure Direct Object Reference (IDOR).
CS Cart 4.18.3 is vulnerable to Insecure Direct Object Reference (IDOR). The user profile functionality allows enabling or disabling stickers through a parameter (company_id) sent in the request. However, this operation is not properly validated on the server side. An authenticated user can manipulate the request to target other users' accounts and toggle the sticker setting by modifying the company_id or other object identifiers.
Security readout for executives and security teams
Plain-English summary
CVE-2025-50849 is a reported IDOR flaw in CS-Cart 4.18.3. An authenticated user may be able to change an object identifier in a profile-related request and affect another account's sticker setting. Treat this as high priority for exposed CS-Cart deployments, but the provided sources do not confirm a vendor patch or real-world exploitation.
Executive priority
High priority for CS-Cart 4.18.3 environments because authenticated users may affect another account's settings. Business urgency depends on deployment exposure, user trust model, and whether the affected profile operation maps to sensitive customer or merchant workflows.
Technical view
The issue is described as CWE-639: authorization bypass through user-controlled key. The vulnerable profile functionality accepts company_id or similar identifiers without sufficient server-side validation. CVSS 3.1 is 8.0 high with low attack complexity and low privileges required. Available evidence is limited to the CVE record and referenced researcher write-up.
Likely exposure
Likely exposure is limited to organizations running CS-Cart 4.18.3 with authenticated user access to profile functionality. The sources do not establish whether other CS-Cart versions, editions, plugins, or configurations are affected.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Exploitation requires an authenticated user and interaction per the CVSS vector. Do not assume internet-wide exploitation from the available evidence.
Researcher notes
Evidence is narrow. The description centers on toggling sticker settings through company_id manipulation, while CVSS rates confidentiality, integrity, and availability as high. Validate actual business impact in the target application before expanding scope beyond the reported behavior.
Mitigation direction
Check CS-Cart vendor guidance for fixed versions or official workarounds.
Prioritize remediation for CS-Cart 4.18.3 instances with external user accounts.
Enforce server-side authorization on company_id and related object identifiers.
Restrict profile-setting changes to trusted users where operationally feasible.
Monitor account/profile changes for cross-account object identifier misuse.
Validation and detection
Inventory CS-Cart deployments and confirm any version 4.18.3 exposure.
Review profile-setting handlers for ownership checks before object updates.
Check logs for users modifying records tied to other company_id values.
Track the CVE record and vendor channels for patch confirmation.
Regression-test that authenticated users cannot alter another account's settings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.