Security readout for executives and security teams
Plain-English summary
osTicket v1.18.2 has a flaw in its password reset page that lets an unauthenticated attacker figure out which usernames actually exist on the system. This does not directly steal data or take over accounts, but it hands attackers a validated list of real users they can target with phishing, password spraying, or credential stuffing.
Executive priority
Treat as a moderate, non-emergency hardening item. It will not, by itself, breach the environment, but it accelerates phishing and credential attacks against your support portal users. Prioritize patching, rate limiting, and MFA on any internet-facing osTicket instance within the normal maintenance cycle.
Technical view
The /pwreset.php endpoint in osTicket 1.18.2 exhibits an observable discrepancy (CWE-203) between responses or timing for valid versus invalid usernames. A remote, unauthenticated attacker can iterate candidate usernames and infer which are registered. CVSS 3.1 is 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), reflecting low confidentiality impact without integrity or availability effects.
Likely exposure
Any internet-facing osTicket 1.18.2 instance that exposes the password reset workflow is likely affected. Exposure is broadest for organizations that publish their osTicket portal for customer or partner support without rate limiting, WAF protections, or account-lockout hardening in front of the reset page.
Exploitation context
No public exploitation is cited in the source bundle, and CISA KEV does not list this CVE. The referenced csacyber.com writeup describes the timing-based disclosure conceptually. Exploitation requires only network access and username lists, so opportunistic reconnaissance against exposed osTicket portals is plausible even without a public tool.
Researcher notes
CWE-203 observable discrepancy on /pwreset.php in osTicket 1.18.2. The source bundle does not name a fixed version, patched commit, or public PoC, and lists no CPEs. Validate by comparing HTTP response content, status, and latency for valid versus invalid usernames. Combine with rate-limit testing. Confirm scope against other authentication endpoints (login, signup) that may share the same disclosure pattern.
Mitigation direction
- Confirm osTicket version and upgrade to a fixed release per vendor guidance once available.
- Place a WAF or reverse proxy in front of /pwreset.php with strict rate limiting.
- Enforce uniform response content and timing for the password reset workflow.
- Restrict staff/admin portals to VPN or IP allowlists where feasible.
- Monitor authentication and reset endpoints for enumeration-style traffic patterns.
- Require strong passwords and MFA to blunt downstream credential attacks.
Validation and detection
- Inventory osTicket deployments and identify any running v1.18.2 or earlier.
- Review web server and application logs for high-volume, low-diversity requests to /pwreset.php.
- In an authorized test, submit known-valid and known-invalid usernames and compare response bodies, codes, and timing.
- Verify WAF or rate-limit rules trigger on repeated reset attempts from a single source.
- Check vendor advisories and the cited references for an official patched version.
- Confirm MFA and lockout policies are enforced for all user classes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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.
Open ATT&CK lookupCVE-2026-26895 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://csacyber.com/blog/osticket-timing-vulnerability-understanding-the-riskCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.