CVE-2026-55584: Phpsysinfo/phpsysinfo PhpSysInfo Has An IP Allowlist Vulnerability

HIGH
Advisory Identifier: GHSA-786w-p5pm-cvgh
CVSS 7.5
CWE-290
Published
Advisory Summary

CVE-2026-55584 is a HIGH (CVSS 7.5) phpsysinfo has an ip allowlist vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting Phpsysinfo/phpsysinfo libraries in the Packagist ecosystem. The issue involves phpsysinfo has an ip allowlist (psi_allowed) bypass via spoofed x-forwarded-for / client-ip headers. Remediation is available by upgrading affected packages to version 3.4.6.

CVE-2026-55584 at a Glance

CVE Identifier CVE-2026-55584
GHSA Identifier GHSA-786w-p5pm-cvgh
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-290: Authentication Bypass by Spoofing
Affected Product Phpsysinfo/phpsysinfo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-55584

To remediate this vulnerability, upgrade all affected Phpsysinfo/phpsysinfo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

phpsysinfo/phpsysinfo fixed: 3.4.6
Upgrade phpsysinfo/phpsysinfo to 3.4.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for phpsysinfo/phpsysinfo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-55584, inspect your project dependencies for Phpsysinfo/phpsysinfo:

inspect dependencies for phpsysinfo/phpsysinfo

Analyze the terminal output to locate any version of Phpsysinfo/phpsysinfo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.4.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-290: Authentication Bypass by Spoofing, where this attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. In Phpsysinfo/phpsysinfo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary phpSysInfo'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: <an allowed IP>` to impersonate a trusted address and gain full access to all exposed system information, defeating the only IP-based access restriction the application provides. ## Affected component - File: `read_config.php` - Versions: all versions up to and including 3.4.x (current `main`) ## Description When `PSI_ALLOWED` is configured, `read_config.php` enforces an IP allowlist. The client IP is resolved as follows: ```php if (isset($_SERVER["HTTP_X_FORWARDED_FOR"])) { $ip = $_SERVER["HTTP_X_FORWARDED_FOR"]; } else { if (isset($_SERVER["HTTP_CLIENT_IP"])) { $ip = $_SERVER["HTTP_CLIENT_IP"]; } else { $ip = $_SERVER["REMOTE_ADDR"]; } } ``` 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. ## Proof of Concept Verified against phpSysInfo `3.4.x-main-d786ab2` running in a local Docker container (`php:8.2-apache`). Deployment with the allowlist (under `[main]`) restricted to an address the attacker does not own: ```ini ; phpsysinfo.ini ([main] section) ALLOWED=8.8.8.8 ``` Request without the spoofed header — correctly denied (attacker's real IP is the container gateway `172.17.0.1`): ```bash $ curl -s http://localhost:8080/xml.php | head -c 200 Client IP address (172.17.0.1) not allowed. ``` Request with a spoofed `X-Forwarded-For` matching the allowlist — bypass, full system information returned: ```bash $ curl -s -H "X-Forwarded-For: 8.8.8.8" http://localhost:8080/xml.php | head -c 200 <?xml version="1.0" encoding="UTF-8"?> <tns:phpsysinfo xmlns:tns="http://phpsysinfo.sourceforge.net/" ...> ``` The same bypass works with the `Client-IP` header (`HTTP_CLIENT_IP`), which is also trusted before `REMOTE_ADDR`. ## Impact Any remote, unauthenticated attacker can defeat the `PSI_ALLOWED` access restriction and read the complete system information exposed by phpSysInfo, including hostname, kernel version, CPU model, memory layout, mounted filesystems, and all network interface addresses. This information is valuable for reconnaissance and targeting of further attacks. ## Remediation Use `REMOTE_ADDR` as the authoritative client IP by default. Only honor `X-Forwarded-For` / `Client-IP` when the request originates from an explicitly configured list of trusted proxies, and when honoring it, parse the correct entry from the chain rather than trusting the whole header. Example direction: ```php $ip = $_SERVER["REMOTE_ADDR"]; if (defined('PSI_TRUSTED_PROXIES') && in_array($ip, $trusted_proxies, true) && isset($_SERVER["HTTP_X_FORWARDED_FOR"])) { // take the right-most untrusted hop from the XFF chain $parts = array_map('trim', explode(',', $_SERVER["HTTP_X_FORWARDED_FOR"])); $ip = end($parts); } ``` ## Discovery / Credit - Reported by: Muhammed Mirac Kayıkci - Coordinated disclosure; no third-party systems were tested. Verification performed against a local Docker deployment only.

CVE-2026-55584 Affected Phpsysinfo/phpsysinfo Versions

1 component(s)
Fixed Versions:
3.4.6
Product / Package Ecosystem Affected Versions Fixed Version
phpsysinfo/phpsysinfo
Packagist
< 3.4.6
3.4.6

References

Frequently Asked Questions

What is CVE-2026-55584?
CVE-2026-55584 is a security vulnerability in Phpsysinfo/phpsysinfo involving phpSysInfo has an IP allowlist (PSI_ALLOWED) bypass via spoofed X-Forwarded-For / Client-IP headers under CWE-290: Authentication Bypass by Spoofing.
Which Phpsysinfo/phpsysinfo versions are affected?
Affected versions include releases prior to 3.4.6 across affected packages: phpsysinfo/phpsysinfo.
What version fixes CVE-2026-55584?
Upgrading to 3.4.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is phpsysinfo/phpsysinfo affected?
Yes, phpsysinfo/phpsysinfo is affected in releases prior to 3.4.6. Upgrade your dependency to 3.4.6 or later.
What is the CVSS score of CVE-2026-55584?
CVE-2026-55584 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-55584?
CVE-2026-55584 is classified under CWE-290: Authentication Bypass by Spoofing (This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.).
How can I check Packagist dependencies for CVE-2026-55584?
Run the dependency tree command: 'inspect dependencies for phpsysinfo/phpsysinfo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-786w-p5pm-cvgh",
  "modified" : "2026-08-28T18:30:55Z",
  "published" : "2026-08-28T18:30:55Z",
  "aliases" : [ "CVE-2026-55584" ],
  "summary" : "phpSysInfo has an IP allowlist (PSI_ALLOWED) bypass via spoofed X-Forwarded-For / Client-IP headers",
  "details" : "## Summary\nphpSysInfo'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: <an allowed IP>` to impersonate a trusted address and gain full access to all exposed system information, defeating the only IP-based access restriction the application provides.\n\n## Affected component\n- File: `read_config.php`\n- Versions: all versions up to and including 3.4.x (current `main`)\n\n## Description\nWhen `PSI_ALLOWED` is configured, `read_config.php` enforces an IP allowlist. The client IP is resolved as follows:\n\n```php\nif (isset($_SERVER[\"HTTP_X_FORWARDED_FOR\"])) {\n    $ip = $_SERVER[\"HTTP_X_FORWARDED_FOR\"];\n} else {\n    if (isset($_SERVER[\"HTTP_CLIENT_IP\"])) {\n        $ip = $_SERVER[\"HTTP_CLIENT_IP\"];\n    } else {\n        $ip = $_SERVER[\"REMOTE_ADDR\"];\n    }\n}\n```\n\nBoth `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.\n\n## Proof of Concept\nVerified against phpSysInfo `3.4.x-main-d786ab2` running in a local Docker container (`php:8.2-apache`).\n\nDeployment with the allowlist (under `[main]`) restricted to an address the attacker does not own:\n\n```ini\n; phpsysinfo.ini  ([main] section)\nALLOWED=8.8.8.8\n```\n\nRequest without the spoofed header — correctly denied (attacker's real IP is the container gateway `172.17.0.1`):\n\n```bash\n$ curl -s http://localhost:8080/xml.php | head -c 200\nClient IP address (172.17.0.1) not allowed.\n```\n\nRequest with a spoofed `X-Forwarded-For` matching the allowlist — bypass, full system information returned:\n\n```bash\n$ curl -s -H \"X-Forwarded-For: 8.8.8.8\" http://localhost:8080/xml.php | head -c 200\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<tns:phpsysinfo xmlns:tns=\"http://phpsysinfo.sourceforge.net/\" ...>\n```\n\nThe same bypass works with the `Client-IP` header (`HTTP_CLIENT_IP`), which is also trusted before `REMOTE_ADDR`.\n\n## Impact\nAny remote, unauthenticated attacker can defeat the `PSI_ALLOWED` access restriction and read the complete system information exposed by phpSysInfo, including hostname, kernel version, CPU model, memory layout, mounted filesystems, and all network interface addresses. This information is valuable for reconnaissance and targeting of further attacks.\n\n## Remediation\nUse `REMOTE_ADDR` as the authoritative client IP by default. Only honor `X-Forwarded-For` / `Client-IP` when the request originates from an explicitly configured list of trusted proxies, and when honoring it, parse the correct entry from the chain rather than trusting the whole header. Example direction:\n\n```php\n$ip = $_SERVER[\"REMOTE_ADDR\"];\nif (defined('PSI_TRUSTED_PROXIES') && in_array($ip, $trusted_proxies, true)\n    && isset($_SERVER[\"HTTP_X_FORWARDED_FOR\"])) {\n    // take the right-most untrusted hop from the XFF chain\n    $parts = array_map('trim', explode(',', $_SERVER[\"HTTP_X_FORWARDED_FOR\"]));\n    $ip = end($parts);\n}\n```\n\n## Discovery / Credit\n- Reported by: Muhammed Mirac Kayıkci\n- Coordinated disclosure; no third-party systems were tested. Verification performed against a local Docker deployment only.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "phpsysinfo/phpsysinfo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.4.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.4.5"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/phpsysinfo/phpsysinfo/security/advisories/GHSA-786w-p5pm-cvgh"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/phpsysinfo/phpsysinfo/commit/019fa2d7e568ea11461adb4bd33da5dc87c4b9ab"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/phpsysinfo/phpsysinfo"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/phpsysinfo/phpsysinfo/releases/tag/v3.4.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-290" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T18:30:55Z",
    "nvd_published_at" : null
  }
}