Description
phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does not require the current password when changing an account e-mail in the user control panel (UserController::updateData, api/user/data/update), checking only the session and CSRF token. An attacker with a hijacked session can set the e-mail to their own mailbox and use the password-reset flow to take over non-2FA accounts, including superadmin.
Published: 2026-10-17
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Account takeover
Action: Immediate Patch
AI Analysis

Impact

The vulnerability in phpMyFAQ allows an attacker who has hijacked a user session to change the account e‑mail address without providing the current password. Once the e‑mail is changed, the attacker can initiate the password‑reset workflow and take over accounts that do not have two‑factor authentication enabled, including super‑administrator accounts. The weakness resides in an inadequate authorization check (CWE‑308).

Affected Systems

All installations of phpMyFAQ from vendor thorsten, prior to version 4.1.9 and 4.2.0‑alpha before 4.2.0‑beta, are affected. The issue occurs in the user control panel handling "UserController::updateData" and the API endpoint "api/user/data/update".

Risk and Exploitability

The CVSS score of 8.7 indicates a high severity for this flaw. The EPSS score is not available, but the lack of a current‑password check makes exploitation straightforward for anyone who can hijack a session. The vulnerability is not currently listed in the CISA KEV catalog. The likely attack vector requires session hijacking; the attacker does not need any privileged user credentials. Once a session is compromised, changing the e‑mail followed by a password reset enables the attacker to fully control the account.

Generated by OpenCVE AI on October 17, 2026 at 20:58 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to a version that enforces the current password when changing account e‑mail (4.1.9 or later, or 4.2.0‑alpha ≥4.2.0‑beta), which is the official vendor fix.
  • If an immediate upgrade is not possible, block or tightly monitor session hijacking by enforcing strict session timeouts and IP binding to mitigate the risk of unauthorized session changes.
  • Implement additional validation that requires the user to re‑enter their password before any sensitive account changes, which mitigates the missing step‑up issue even if the upstream patch is delayed.

Generated by OpenCVE AI on October 17, 2026 at 20:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 17 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
Description phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does not require the current password when changing an account e-mail in the user control panel (UserController::updateData, api/user/data/update), checking only the session and CSRF token. An attacker with a hijacked session can set the e-mail to their own mailbox and use the password-reset flow to take over non-2FA accounts, including superadmin.
Title phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Missing Current-Password Step-Up on E-mail Change Enables Account Takeover
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-308
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L'}

cvssV4_0

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


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-18T12:18:30.268Z

Reserved: 2026-10-17T12:15:56.789Z

Link: CVE-2026-111884

cve-icon Vulnrichment

Updated: 2026-10-18T12:18:15.766Z

cve-icon NVD

Status : Deferred

Published: 2026-10-17T19:16:29.450

Modified: 2026-10-18T13:16:35.800

Link: CVE-2026-111884

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-17T21:00:14Z

Weaknesses
  • CWE-308

    Use of Single-factor Authentication