Security readout for executives and security teams
Plain-English summary
CVE-2026-35675 affects phpMyFAQ before 4.1.3. The password reset API could allow an unauthenticated attacker to reset another user’s password without proper reset-token or email confirmation checks. If an administrator account is targeted, the attacker could take over the phpMyFAQ instance.
Executive priority
Treat as urgent for any exposed phpMyFAQ deployment. Account takeover of knowledge-base administration can affect data integrity, internal trust, and operational continuity.
Technical view
The issue is in /api/user/password/update. Public advisories describe missing password reset token verification, enabling unauthenticated password changes for valid accounts. The CVSS 4.0 score is 8.8 with network access, low complexity, no privileges, and no user interaction required.
Likely exposure
Organizations running internet-accessible or internally reachable phpMyFAQ versions before 4.1.3 are exposed. Risk is highest where phpMyFAQ accounts have administrative privileges or reused credentials could create downstream impact.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. However, the vulnerability is remotely reachable, unauthenticated, and tied to account takeover, making timely remediation important.
Researcher notes
Evidence comes from CVE, GitHub Security Advisory, and VulnCheck. The bundle states affected versions are before 4.1.3. Do not assume exploitation in the wild without new supporting sources.
Mitigation direction
- Upgrade phpMyFAQ to 4.1.3 or later.
- Review vendor advisory for any additional hardening guidance.
- Restrict access to phpMyFAQ if immediate upgrade is not possible.
- Monitor phpMyFAQ accounts for unexpected password changes.
Validation and detection
- Inventory phpMyFAQ deployments and confirm version numbers.
- Check whether any deployment is older than 4.1.3.
- Review logs for suspicious password reset activity.
- Confirm administrative accounts have not been unexpectedly modified.
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-307: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-35675 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
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA: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
2 official scoresWe 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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N3.94.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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
- GHSA Advisory GHSA-w9xh-5f39-vq89CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: phpMyFAQ - Authentication Bypass via Missing Password Reset Token in /api/user/password/updateCVE reference, VulnCheck · third-party-advisory
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.
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.