CVE-2018-7195
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 · uneditedEnhancesoft osTicket before 1.10.2 allows remote attackers to reset arbitrary passwords (when an associated e-mail address is known) by leveraging guest access and guessing a 6-digit number.
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 confidenceEnhancesoft osTicket before version 1.10.2 contains a password reset mechanism that uses a weak 6-digit token, allowing remote attackers with guest access to reset arbitrary user passwords by guessing the token when the target email address is known. This is effectively a brute-force vulnerability in the password reset flow.
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<= 1.10.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed osTicket versionLocate the version file (scp/VERSION.php or similar) or check the system information in the admin panel. The file typically contains a version string like 'v1.10.1' or similar.Affected if The installed version is 1.10.1 or earlier (anything <= 1.10.1). Versions 1.10.2 and later are not affected.
-
Confirm guest access is enabledCheck the osTicket configuration settings under Admin > Settings > General to see if 'Guest Ticket Creation' or unauthenticated access is permitted.Affected if Guest access is enabled, allowing unauthenticated users to access the password reset functionality.
-
Inspect the password reset token generation mechanismExamine the source code file responsible for password reset (typically include/class.auth.php or similar password reset handler) to determine if the token is generated using a weak 6-digit numeric code.Affected if The code generates a token consisting of only 6 digits (100000-999999 range), making it susceptible to brute-force attacks.
-
Check for rate limiting on password reset endpointReview web server configuration (Apache/Nginx) or osTicket settings for any rate-limiting or account lockout controls applied to the /pwreset.php endpoint or password reset form submissions.Affected if No rate limiting, CAPTCHA, or account lockout mechanism is present on the password reset functionality.
You are affected if your osTicket version is 1.10.1 or earlier AND guest access is enabled AND the password reset uses a 6-digit numeric token without rate limiting.
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 dataUpgrade osTicket to version 1.10.2 or later, which implements cryptographically stronger reset tokens. If upgrading is not immediately possible, consider rate-limiting password reset attempts as an interim control.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2018-7195 — 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-2018-7195 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