<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 14:55:07 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-47156</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-47156</link>
      <description>&lt;p&gt;MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API&amp;#39;s mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target&amp;#39;s password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser&amp;#39;s MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API&amp;#39;s AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API&amp;#39;s mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target&amp;#39;s password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser&amp;#39;s MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API&amp;#39;s AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-47156</guid>
    </item>
    <item>
      <title>GHSA-c2xg-qjqw-2v98 — MantisBT: SOAP API Authentication Bypass with Privilege Escalation to Administrator</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-c2xg-qjqw-2v98</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: mantisbt/mantisbt&lt;/p&gt;
&lt;p&gt;MantisBT 2.28.3 and earlier contains a critical authentication bypass in the SOAP API&amp;#39;s mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target&amp;#39;s password.&lt;/p&gt;
&lt;p&gt;The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser&amp;#39;s MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API.&lt;/p&gt;
&lt;p&gt;The REST API is NOT affected. The REST API&amp;#39;s AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed.&lt;/p&gt;
&lt;p&gt;The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client.&lt;/p&gt;
&lt;p&gt;### Impact
- Full administrator access to the SOAP API from zero prior access (with self-registration enabled, which is the default)
- Read/write all issues including private issues and notes across all projects
- Full data exfiltration of all bug reports, attachments, user accounts (id, name, email), and non-private configuration values via the 71 SOAP operations available
- Destructive operations: delete projects, issues, attachm…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: mantisbt/mantisbt&lt;/p&gt;
&lt;p&gt;MantisBT 2.28.3 and earlier contains a critical authentication bypass in the SOAP API&amp;#39;s mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target&amp;#39;s password.&lt;/p&gt;
&lt;p&gt;The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser&amp;#39;s MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API.&lt;/p&gt;
&lt;p&gt;The REST API is NOT affected. The REST API&amp;#39;s AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed.&lt;/p&gt;
&lt;p&gt;The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client.&lt;/p&gt;
&lt;p&gt;### Impact
- Full administrator access to the SOAP API from zero prior access (with self-registration enabled, which is the default)
- Read/write all issues including private issues and notes across all projects
- Full data exfiltration of all bug reports, attachments, user accounts (id, name, email), and non-private configuration values via the 71 SOAP operations available
- Destructive operations: delete projects, issues, attachm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-c2xg-qjqw-2v98</guid>
    </item>
  </channel>
</rss>
