Description
phpMyFAQ versions before 4.1.8 fail to validate CAPTCHA when the store parameter is set to 'now' in question submission requests. Unauthenticated attackers can bypass CAPTCHA protection and submit unlimited questions directly, causing database pollution and triggering outgoing mail notifications.
Published: 2026-09-04
Score: 6.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

phpMyFAQ versions before 4.1.8 do not validate the CAPTCHA field when the "store" parameter is set to "now" in question submission requests. This flaw permits unauthenticated users to circumvent the CAPTCHA protection and submit unlimited questions to the system. The resulting database pollution can lead to excessive storage consumption, and each accepted question triggers outgoing email notifications, potentially resulting in spam or denial of service through message flooding.

Affected Systems

The vulnerability affects the phpMyFAQ application provided by thorsten. Any instance running a version earlier than 4.1.8 is susceptible. The affected product is commonly deployed in web forums and knowledge bases where users can submit questions.

Risk and Exploitability

The flaw carries a CVSS score of 6.9, indicating moderate to high severity. While an explicit EPSS score is not available, the vulnerability is exploitable remotely via standard HTTP requests without authentication. The vendor has not listed it in the CISA KEV catalog, but the potential for widespread spam emails and database corruption makes it a significant risk for organizations running vulnerable installations.

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

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.8 or later, which enforces proper CAPTCHA validation.
  • If an immediate upgrade is not feasible, restrict the "store" parameter to acceptable values or disable the "store=now" feature through application configuration to prevent automated submissions.
  • Monitoring should be enabled to detect unusual question entries and excessive outgoing email traffic, and temporary rate limits or spam filters should be applied until the issue is resolved.

Generated by OpenCVE AI on September 4, 2026 at 12:29 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 fail to validate CAPTCHA when the store parameter is set to 'now' in question submission requests. Unauthenticated attackers can bypass CAPTCHA protection and submit unlimited questions directly, causing database pollution and triggering outgoing mail notifications.
Title phpMyFAQ before 4.1.8 CAPTCHA Bypass via store parameter
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-799
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV4_0

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


Subscriptions

Phpmyfaq Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

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

Reserved: 2026-09-04T10:56:22.465Z

Link: CVE-2026-85586

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-85586

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

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

Weaknesses
  • CWE-799

    Improper Control of Interaction Frequency