<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T12:06:01.793855+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-56737</id>
    <title>fkie_cve-2026-56737</title>
    <updated>2026-09-29T12:06:03.644314+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-forced six-digit TOTP code without first authenticating with the account password, allowing takeover of any 2FA-enabled account, including administrator accounts. Version 4.1.6 is patched by binding TOTP verification to a session established after successful password authentication and limiting failed TOTP attempts. No official workaround is documented; affected installations should upgrade to 4.1.6 or later.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-56737"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8gpw-xvpf-hvx5</id>
    <title>GHSA-8gpw-xvpf-hvx5 — phpMyFAQ's two-factor authentication login bypasses the password factor</title>
    <updated>2026-09-29T12:06:03.644455+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: thorsten/phpmyfaq, Packagist: phpmyfaq/phpmyfaq</p>
<p>### Summary
The public two-factor verification endpoint `POST /check` logs a user in based **solely** on a valid
6-digit TOTP token and a chosen `user-id`. It does **not** require — and is not bound to — a prior
successful password authentication. For any account that has 2FA enabled, an unauthenticated attacker
can authenticate **without knowing the password**, reducing the account to a single factor (a 6-digit
code) that is itself brute-forceable because this endpoint has no lockout (see Finding #2). This is an
authentication bypass of the primary credential for all 2FA-protected accounts, including administrators.</p>
<p>### Details
`src/phpMyFAQ/Controller/Frontend/AuthenticationController.php:255-283`:</p>
<p>```php
#[Route(path: '/check', name: 'public.auth.check', methods: ['POST'])]
public function check(Request $request): RedirectResponse
{
    if ($this-&gt;currentUser-&gt;isLoggedIn()) {
        return new RedirectResponse(url: './');
    }</p>
<p>$token  = Filter::filterVar($request-&gt;request-&gt;get('token'), FILTER_SANITIZE_SPECIAL_CHARS);
    $userId = (int) Filter::filterVar($request-&gt;request-&gt;get('user-id'), FILTER_VALIDATE_INT);</p>
<p>if ($userId &lt;= 0) { /* ... */ }</p>
<p>$this-&gt;currentUserService-&gt;getUserById($userId);          // loads attacker-chosen user</p>
<p>if (strlen((string) $token) === 6) {
        $result = $this-&gt;twoFactor-&gt;validateToken($token, $userId);
        if ($result) {
            $this-&gt;currentUserService-&gt;twoFactorSuccess();    // full login, no password ever c…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8gpw-xvpf-hvx5"/>
  </entry>
</feed>
