Description
phpMyFAQ 4.0.0 before 4.1.9 contains a cross-site request forgery vulnerability in the POST /admin/api/update-database endpoint, which executes database migrations without validating a CSRF token. Attackers can lure a logged-in user with the CONFIGURATION_EDIT permission into submitting a crafted cross-site request, triggering migrations that may impact database integrity or availability.
Published: 2026-10-17
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Database integrity and availability
Action: Apply Patch
AI Analysis

Impact

The vulnerability is a cross‑site request forgery in the POST /admin/api/update-database endpoint of phpMyFAQ. The endpoint runs database migrations when a request is received without verifying a CSRF token. An attacker can trick a logged‑in user who has the CONFIGURATION_EDIT permission into submitting a forged request, causing unintended schema changes or data alterations that compromise database integrity or disrupt service availability.

Affected Systems

The affected product is phpMyFAQ provided by Thorsten. Versions 4.0.0 through 4.1.8 are vulnerable. Versions 4.1.9 and later include the fix that validates a CSRF token before running migrations.

Risk and Exploitability

With a CVSS score of 7.1 the vulnerability is moderate in severity. The EPSS score is not provided, and the flaw is not listed in the CISA KEV catalog, indicating no known active exploitation at this time. The likely attack vector is a crafted cross‑site request from a malicious website or malicious script that triggers the POST request while the victim is. Exploitation requires an authenticated user with configuration‑edit rights, so the risk is limited to users who have that permission, but once triggered the attacker can alter or disrupt the database. Overall the risk is moderate and should be mitigated promptly.

Generated by OpenCVE AI on October 17, 2026 at 21:18 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest phpMyFAQ release (4.1.9 or newer) to restore CSRF validation on the update‑database endpoint
  • Restrict administrative access by network segmentation or IP whitelisting to limit exposure to users with CONFIGURATION_EDIT permission
  • Deploy web‑application firewall or browser‑side CSRF defenses that reject cross‑domain POST requests lacking a valid token

Generated by OpenCVE AI on October 17, 2026 at 21:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

Type Values Removed Values Added
Description phpMyFAQ 4.0.0 before 4.1.9 contains a cross-site request forgery vulnerability in the POST /admin/api/update-database endpoint, which executes database migrations without validating a CSRF token. Attackers can lure a logged-in user with the CONFIGURATION_EDIT permission into submitting a crafted cross-site request, triggering migrations that may impact database integrity or availability.
Title phpMyFAQ 4.0.0 before 4.1.9 CSRF via /admin/api/update-database
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-352
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

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

cvssV4_0

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


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-19T16:39:51.053Z

Reserved: 2026-10-17T12:18:07.314Z

Link: CVE-2026-111907

cve-icon Vulnrichment

Updated: 2026-10-19T15:42:27.680Z

cve-icon NVD

Status : Deferred

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

Modified: 2026-10-19T17:17:05.593

Link: CVE-2026-111907

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-17T21:30:06Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)