<?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>Sat, 03 Oct 2026 04:37:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55584</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55584</link>
      <description>&lt;p&gt;phpSysInfo is a customizable PHP script that displays system information. Prior to 3.4.6, the PSI_ALLOWED access-control check in read_config.php trusts attacker-controlled X-Forwarded-For and Client-IP HTTP headers before REMOTE_ADDR. A remote unauthenticated attacker can supply an allowed address in one of these headers to impersonate a trusted client and access exposed hostname, kernel, CPU, memory, filesystem, and network-interface information. This issue is fixed in version 3.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;phpSysInfo is a customizable PHP script that displays system information. Prior to 3.4.6, the PSI_ALLOWED access-control check in read_config.php trusts attacker-controlled X-Forwarded-For and Client-IP HTTP headers before REMOTE_ADDR. A remote unauthenticated attacker can supply an allowed address in one of these headers to impersonate a trusted client and access exposed hostname, kernel, CPU, memory, filesystem, and network-interface information. This issue is fixed in version 3.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55584</guid>
    </item>
    <item>
      <title>GHSA-786w-p5pm-cvgh — phpSysInfo has an IP allowlist (PSI_ALLOWED) bypass via spoofed X-Forwarded-For / Client-IP headers</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-786w-p5pm-cvgh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpsysinfo/phpsysinfo&lt;/p&gt;
&lt;p&gt;## Summary
phpSysInfo&amp;#39;s `PSI_ALLOWED` IP allowlist can be trivially bypassed by any unauthenticated remote attacker. The access-control check in `read_config.php` derives the client IP from the attacker-controlled `X-Forwarded-For` and `Client-IP` HTTP headers **before** falling back to `REMOTE_ADDR`. An attacker can send `X-Forwarded-For: &amp;lt;an allowed IP&amp;gt;` to impersonate a trusted address and gain full access to all exposed system information, defeating the only IP-based access restriction the application provides.&lt;/p&gt;
&lt;p&gt;## Affected component
- File: `read_config.php`
- Versions: all versions up to and including 3.4.x (current `main`)&lt;/p&gt;
&lt;p&gt;## Description
When `PSI_ALLOWED` is configured, `read_config.php` enforces an IP allowlist. The client IP is resolved as follows:&lt;/p&gt;
&lt;p&gt;```php
if (isset($_SERVER[&amp;#34;HTTP_X_FORWARDED_FOR&amp;#34;])) {
    $ip = $_SERVER[&amp;#34;HTTP_X_FORWARDED_FOR&amp;#34;];
} else {
    if (isset($_SERVER[&amp;#34;HTTP_CLIENT_IP&amp;#34;])) {
        $ip = $_SERVER[&amp;#34;HTTP_CLIENT_IP&amp;#34;];
    } else {
        $ip = $_SERVER[&amp;#34;REMOTE_ADDR&amp;#34;];
    }
}
```&lt;/p&gt;
&lt;p&gt;Both `HTTP_X_FORWARDED_FOR` and `HTTP_CLIENT_IP` are fully attacker-controlled request headers. They are trusted unconditionally and take priority over `REMOTE_ADDR`. There is no concept of a configured/trusted reverse proxy, so even when phpSysInfo is exposed directly (no proxy in front), the spoofed header wins. As a result the allowlist provides no real protection.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
Verified against phpSysInfo `3.4.x-main-d786ab2` running in a local Docker co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpsysinfo/phpsysinfo&lt;/p&gt;
&lt;p&gt;## Summary
phpSysInfo&amp;#39;s `PSI_ALLOWED` IP allowlist can be trivially bypassed by any unauthenticated remote attacker. The access-control check in `read_config.php` derives the client IP from the attacker-controlled `X-Forwarded-For` and `Client-IP` HTTP headers **before** falling back to `REMOTE_ADDR`. An attacker can send `X-Forwarded-For: &amp;lt;an allowed IP&amp;gt;` to impersonate a trusted address and gain full access to all exposed system information, defeating the only IP-based access restriction the application provides.&lt;/p&gt;
&lt;p&gt;## Affected component
- File: `read_config.php`
- Versions: all versions up to and including 3.4.x (current `main`)&lt;/p&gt;
&lt;p&gt;## Description
When `PSI_ALLOWED` is configured, `read_config.php` enforces an IP allowlist. The client IP is resolved as follows:&lt;/p&gt;
&lt;p&gt;```php
if (isset($_SERVER[&amp;#34;HTTP_X_FORWARDED_FOR&amp;#34;])) {
    $ip = $_SERVER[&amp;#34;HTTP_X_FORWARDED_FOR&amp;#34;];
} else {
    if (isset($_SERVER[&amp;#34;HTTP_CLIENT_IP&amp;#34;])) {
        $ip = $_SERVER[&amp;#34;HTTP_CLIENT_IP&amp;#34;];
    } else {
        $ip = $_SERVER[&amp;#34;REMOTE_ADDR&amp;#34;];
    }
}
```&lt;/p&gt;
&lt;p&gt;Both `HTTP_X_FORWARDED_FOR` and `HTTP_CLIENT_IP` are fully attacker-controlled request headers. They are trusted unconditionally and take priority over `REMOTE_ADDR`. There is no concept of a configured/trusted reverse proxy, so even when phpSysInfo is exposed directly (no proxy in front), the spoofed header wins. As a result the allowlist provides no real protection.&lt;/p&gt;
&lt;p&gt;## Proof of Concept
Verified against phpSysInfo `3.4.x-main-d786ab2` running in a local Docker co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-786w-p5pm-cvgh</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-55584</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-55584</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: phpsysinfo, Ubuntu:18.04:LTS: phpsysinfo, Ubuntu:20.04:LTS: phpsysinfo, Ubuntu:22.04:LTS: phpsysinfo, Ubuntu:24.04:LTS: phpsysinfo, Ubuntu:26.04:LTS: phpsysinfo&lt;/p&gt;
&lt;p&gt;phpSysInfo is a customizable PHP script that displays system information. Prior to 3.4.6, the PSI_ALLOWED access-control check in read_config.php trusts attacker-controlled X-Forwarded-For and Client-IP HTTP headers before REMOTE_ADDR. A remote unauthenticated attacker can supply an allowed address in one of these headers to impersonate a trusted client and access exposed hostname, kernel, CPU, memory, filesystem, and network-interface information. This issue is fixed in version 3.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: phpsysinfo, Ubuntu:18.04:LTS: phpsysinfo, Ubuntu:20.04:LTS: phpsysinfo, Ubuntu:22.04:LTS: phpsysinfo, Ubuntu:24.04:LTS: phpsysinfo, Ubuntu:26.04:LTS: phpsysinfo&lt;/p&gt;
&lt;p&gt;phpSysInfo is a customizable PHP script that displays system information. Prior to 3.4.6, the PSI_ALLOWED access-control check in read_config.php trusts attacker-controlled X-Forwarded-For and Client-IP HTTP headers before REMOTE_ADDR. A remote unauthenticated attacker can supply an allowed address in one of these headers to impersonate a trusted client and access exposed hostname, kernel, CPU, memory, filesystem, and network-interface information. This issue is fixed in version 3.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-55584</guid>
    </item>
  </channel>
</rss>
