dbcve.org
Peel ShoppingApplication · Peel

CVE-2019-20178

MEDIUM · 6.5 CVSS v3.1 Published 2020-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Advisto PEEL Shopping 9.2.1 has CSRF via administrer/utilisateurs.php to delete a user.

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

Advisto PEEL Shopping 9.2.1 lacks anti-CSRF tokens on the user deletion functionality in administrer/utilisateurs.php. An authenticated administrator visiting a malicious site can be tricked into silently triggering a DELETE request that removes users from the system.

MitigationImplement anti-CSRF tokens on all state-changing operations in the admin panel, validate tokens server-side before executing delete actions, and configure SameSite attribute on session cookies.

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
Peel ShoppingApplication
Affected:= 9.2.1

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Identify installed Peel Shopping version
    Locate the version file or admin panel 'About' page to determine the exact installed version number
    Affected if Installed version is exactly 9.2.1
  2. Locate the vulnerable script
    Check if the file 'administrer/utilisateurs.php' exists in the web root or admin directory
    Affected if The file exists and the product version is 9.2.1
  3. Inspect user deletion functionality
    Open administrer/utilisateurs.php and search for the user deletion code path (DELETE action or user removal logic)
    Affected if The deletion code lacks CSRF token validation (no token check, no $_POST['token'] or $_SESSION['token'] validation before executing delete)
  4. Check session cookie configuration
    Inspect HTTP response headers when logging into the admin panel for the 'SameSite' attribute on session cookies
    Affected if SameSite attribute is missing or not set to 'Strict' or 'Lax' on session cookies

A user is affected if running Peel Shopping version 9.2.1 and the administrer/utilisateurs.php script lacks CSRF token validation on user deletion operations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations in the admin panel, validate tokens server-side before executing delete actions, and configure SameSite attribute on session cookies.

Fix this in Peel Shopping Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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