dbcve.org
PrestashopCMS

CVE-2018-5682

MEDIUM · 5.3 CVSS v3.0 Published 2018-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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
PrestaShop 1.7.2.4 allows user enumeration via the Reset Password feature, by noticing which reset attempts do not produce a "This account does not exist" error message.

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

PrestaShop 1.7.2.4 has a user enumeration vulnerability in its password reset functionality. The application reveals whether an account exists by displaying 'This account does not exist' only for invalid usernames/emails, allowing attackers to enumerate valid user accounts by testing different credentials.

MitigationModify the password reset form to return an identical response (e.g., 'If an account exists with this email, a reset link has been sent') regardless of whether the submitted account exists, preventing attackers from distinguishing valid from invalid accounts.

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
PrestashopCMS
Affected:= 1.7.2.4

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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify PrestaShop version is 1.7.2.4
    Check the version file or footer of your PrestaShop admin dashboard. Common locations include the footer of the back-office pages or a VERSION file in the root installation directory.
    Affected if The installed version equals 1.7.2.4 specifically.
  2. Identify password reset endpoint
    Navigate to the login page and locate the 'Forgot your password?' or password reset link. Note the URL path (typically /password-recovery or similar).
    Affected if The password reset form is accessible and available on the site.
  3. Test with invalid email address
    Submit an email address that you are certain does not exist in the system (e.g., [email protected]) to the password reset form. Record the exact response message displayed.
    Affected if The response explicitly states 'This account does not exist' or similar wording that indicates the email is invalid.
  4. Test with valid email address
    Submit a known-valid email address (such as your own admin account) to the password reset form. Record the exact response message displayed.
    Affected if The response differs from the invalid email response (e.g., shows success message, email sent confirmation, or different error text).
  5. Compare responses for enumeration
    Compare the message received for the invalid email versus the valid email. If they are measurably different and allow you to distinguish between valid and invalid accounts, the vulnerability is present.
    Affected if The system returns different messages for valid vs invalid accounts, allowing an attacker to enumerate which accounts exist.

Your environment is affected if you are running PrestaShop 1.7.2.4 AND the password reset form returns different responses for valid vs invalid accounts, allowing user enumeration.

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

Modify the password reset form to return an identical response (e.g., 'If an account exists with this email, a reset link has been sent') regardless of whether the submitted account exists, preventing attackers from distinguishing valid from invalid accounts.

Fix this in Prestashop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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