CVE-2026-34973

The searchCustomPages() method in phpmyfaq/src/phpMyFAQ/Search.php uses real_escape_string() (via escape()) to sanitize the search term before embedding it in LIKE clauses. However, real_escape_string() does not escape SQL LIKE metacharacters % (match any sequence) and _ (match any single character). An unauthenticated attacker can inject these wildcards into search queries, causing them to match unintended records, including content that was not meant to be surfaced, resulting in information disclosure.

Details

File: phpmyfaq/src/phpMyFAQ/Search.php, lines 226–240

Vulnerable code:

$escapedSearchTerm = $this->configuration->getDb()->escape($searchTerm);
$searchWords = explode(' ', $escapedSearchTerm);
$searchConditions = [];

foreach ($searchWords as $word) {
    if (strlen($word) <= 2) {
        continue;
    }
    $searchConditions[] = sprintf(
        "(page_title LIKE '%%%s%%' OR content LIKE '%%%s%%')",
        $word,
        $word
    );
}

escape() calls mysqli::real_escape_string(), which escapes characters like ', \, NULL, etc., but explicitly does **not** escape % or _, as these are not SQL string delimiters. They are, however, LIKE pattern wildcards.

Attack vector:

A user submits a search term containing _ or % as part of a 3+ character word (to bypass the strlen <= 2 filter). Examples:

• Search for a_b → LIKE becomes '%a_b%' → _ matches any single character, e.g. matches "aXb", "a1b", "azb", broader than the literal string a_b
• Search for te%t → LIKE becomes '%te%t%' → matches test, text, te12t, etc.
• Search for _%_ → LIKE becomes '%_%_%' → matches any record with at least one character, effectively dumping all custom pages

This allows an attacker to retrieve custom page content that would not appear in normal exact searches, bypassing intended search scope restrictions.

PoC

1. Navigate to the phpMyFAQ search page (accessible to unauthenticated users by default).
2. Submit a search query: _%_ (underscore, percent, underscore, length 3, bypasses the <= 2 filter).
3. The backend executes: WHERE (page_title LIKE '%_%_%' OR content LIKE '%_%_%')
4. This matches all custom pages with at least one character in title or content, returning content that would not appear for a specific search term.

• Authentication required: None, search is publicly accessible
• Affected component: searchCustomPages() in Search.php; custom pages (faqcustompages table)
• Impact: Unauthenticated users can enumerate/disclose all custom page content regardless of the intended search term filter
• Fix: Escape % and _ in LIKE search terms before interpolation:

  $word = str_replace(['\\', '%', '_'], ['\\\\', '\\%', '\\_'], $word);
  

  Or use parameterized queries with properly escaped LIKE values.

CVE-2026-34973 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-34973? CVE-2026-34973 is a medium-severity security vulnerability in thorsten/phpmyfaq (composer), affecting versions < 4.1.1. It is fixed in 4.1.1.
2. How severe is CVE-2026-34973? CVE-2026-34973 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of thorsten/phpmyfaq are affected by CVE-2026-34973? thorsten/phpmyfaq (composer) versions < 4.1.1 is affected.
4. Is there a fix for CVE-2026-34973? Yes. CVE-2026-34973 is fixed in 4.1.1. Upgrade to this version or later.
5. Is CVE-2026-34973 exploitable, and should I be worried? Whether CVE-2026-34973 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-34973 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-34973? Upgrade thorsten/phpmyfaq to 4.1.1 or later.