Description
phpMyFAQ versions before 4.1.8 contain an authentication bypass vulnerability in the user control panel API endpoint that allows authenticated attackers to change account passwords without verifying the current password. Attackers with session access can submit a PUT request to the user data update endpoint with only a CSRF token to silently change any user's password, including administrators, causing irreversible account takeover and victim lockout.
Published: 2026-09-04
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability in phpMyFAQ versions prior to 4.1.8 permits an authenticated attacker with session access to change a user's password without verifying the current password. By submitting a PUT request accompanied only by a valid CSRF token to the user data update endpoint, the attacker can silently overwrite any account password, including administrator accounts, resulting in irreversible account takeover and lockout.

Affected Systems

This issue affects installations of the phpMyFAQ application made by the vendor thorsten. All deployments running versions older than 4.1.8 are susceptible. System administrators should verify their installed version and ensure it has been updated to 4.1.8 or a later release.

Risk and Exploitability

The CVSS vector score of 7.1 indicates medium to high severity. Exploitation requires the attacker to already possess a valid authenticated session and the ability to craft a PUT request with an accepted CSRF token. No exploit probability information is available and the vulnerability is not listed as a known exploited vulnerability by CISA. Nevertheless, the ability to perform credential changes without authentication checks represents a serious authorization flaw and warrants prompt remediation.

Generated by OpenCVE AI on September 4, 2026 at 12:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.8 or later to remediate the authentication bypass flaw.
  • Configure the application to require the current password or additional confirmation before processing any account‑change requests, thereby restoring proper authorization checks.
  • Implement strict access controls so that only privileged users can invoke the user‑data update endpoint, and monitor logs for anomalous password‑change activity.

Generated by OpenCVE AI on September 4, 2026 at 12:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
Description phpMyFAQ versions before 4.1.8 contain an authentication bypass vulnerability in the user control panel API endpoint that allows authenticated attackers to change account passwords without verifying the current password. Attackers with session access can submit a PUT request to the user data update endpoint with only a CSRF token to silently change any user's password, including administrators, causing irreversible account takeover and victim lockout.
Title phpMyFAQ before 4.1.8 Authentication Bypass via Unverified Password Change
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-620
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-04T11:29:56.745Z

Reserved: 2026-09-04T10:59:00.162Z

Link: CVE-2026-85591

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T12:17:22.433

Modified: 2026-09-04T12:17:22.433

Link: CVE-2026-85591

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T12:30:17Z

Weaknesses
  • CWE-620

    Unverified Password Change