CVE-2024-50945
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 · uneditedAn improper access control vulnerability exists in SimplCommerce at commit 230310c8d7a0408569b292c5a805c459d47a1d8f, allowing users to submit reviews without verifying if they have purchased the product.
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 confidenceSimplCommerce fails to verify purchase history before allowing users to submit product reviews. The review submission endpoint lacks authorization checks to confirm the user actually purchased the product, allowing any authenticated user to post reviews for any product.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 SimplCommerce installationLook for SimplCommerce-specific files, binaries, or application identifiers in the deployment (e.g., SimplCommerce.dll inbinfolder, or check application headers/footers for 'SimplCommerce' branding).Affected if SimplCommerce is not present in the environment.
-
Determine installed versionCheck the SimplCommerce.dll version property, or look for a version.txt/version.json file in the application root directory, or inspect the csproj file for the SimplCommerce package version.Affected if The installed version cannot be determined or is not documented.
-
Locate the review submission endpointSearch the codebase for review-related controllers (typically ReviewController or similar) and identify the POST endpoint for submitting reviews (commonly /api/reviews or /product/{id}/review).Affected if No review submission endpoint is found in the application.
-
Verify authorization logic existsExamine the review submission method in the backend code. Look for a check that queries the user's order history or purchase records before accepting a review submission. Search for terms like 'purchased', 'order', 'bought', or similar purchase verification logic.Affected if The review submission code contains NO query or validation of the user's purchase history before accepting a review.
-
Test unauthenticated review submissionSubmit a review request to the review endpoint without authentication (without a valid user session or token) and observe if the request is rejected.Affected if The endpoint accepts review submissions without requiring authentication.
-
Test cross-product review submissionUsing an authenticated user account with no purchase history for Product X, attempt to submit a review for Product X. Observe if the review is accepted without purchase verification.Affected if The review is successfully submitted without verifying that the user actually purchased the product.
The environment is affected if SimplCommerce is installed and the review submission endpoint accepts reviews without validating that the authenticated user has a confirmed purchase of the specific product.
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 server-side verification that checks the user's order history before accepting review submissions. Only allow reviews from users with confirmed purchases of the specific product.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50945 — 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-50945 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