GHSA-vrxf-vrc4-22p7
MEDIUMGHSA-vrxf-vrc4-22p7 is a medium-severity (CVSS 5.3) vulnerability in facturascripts/facturascripts. O3 Security confirms whether GHSA-vrxf-vrc4-22p7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
FacturaScripts Vulnerable to Unauthenticated phpinfo() Disclosure via Installer Endpoint
Real-World Exposure
facturascripts/facturascriptsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An unauthenticated information disclosure vulnerability in the Installer controller allows any remote attacker to trigger phpinfo() on a fresh FacturaScripts deployment by requesting /?phpinfo=TRUE, exposing full PHP configuration, server environment variables (including any database credentials, API keys, or application secrets set as env vars), filesystem paths, and loaded extensions without being authenticated.
Details
The phpinfo() debug endpoint was intentionally added in commit 8c31c106 ("Added phpinfo option to the installer") on February 27, 2018, and has remained in the codebase for over 8 years across multiple major versions.
The feature appears to have been added as a convenience tool to help users diagnose PHP configuration during installation. However, it exposes sensitive server information to any unauthenticated attacker who knows the parameter.
Vulnerable code (Core/Controller/Installer.php ~line 115):
if ('TRUE' === $this->request->query('phpinfo', '')) {
phpinfo();
return;
}
This vulnerability is of the same class as CVE-2025-34081 (CONPROSYS HMI System unauthenticated phpinfo() exposure), which received a CVE assignment.
Introduced: commit 8c31c1060581ad6ad591c7689da3a8df8a29f486 (Feb 27 2018) Still present: v2026-39-g262e79208 (confirmed April 2026)
PoC
Prerequisites: Fresh FacturaScripts deployment where installation has not yet been completed (config.php does not contain db_name).
Step 1 — Clone and serve the application: git clone https://github.com/NeoRazorX/facturascripts cd facturascripts php -S localhost:8000
Step 2 — Send the following unauthenticated GET request: GET /?phpinfo=TRUE HTTP/1.1 Host: localhost:8000
Step 3 — Observe full phpinfo() output returned (20+ pages) containing: - Complete PHP configuration - All server environment variables - Filesystem paths - Loaded extensions and versions - HTTP request headers
No credentials, cookies, or prior interaction required.
Tested on: PHP 8.1.34, macOS, fresh clone with no configuration applied. Proof of concept screenshot/PDF available.
Impact
Vulnerability type: Unauthenticated Information Disclosure (CWE-200)
Any unauthenticated remote attacker who can reach a freshly deployed FacturaScripts instance before installation is completed can retrieve the full PHP environment. On production deployments this includes:
- Database credentials (DB_PASSWORD, DB_USER) if set as environment variables
- Application secrets (APP_KEY, JWT secrets) if set as environment variables
- Cloud provider credentials (AWS_SECRET_ACCESS_KEY, etc.) if present
- Full server filesystem paths enabling targeted path traversal attempts
- Exact PHP version and loaded extensions enabling version-specific attacks
- All HTTP headers revealing internal infrastructure details
- Database connection configuration (mysqli default socket, PDO drivers)
- Exact PHP version enabling version-specific CVE targeting (PHP 8.1.34)
Fresh deployments are commonly left unconfigured for extended periods on shared hosting and cloud environments, making this window reliably exploitable in real-world scenarios.
Fix: Remove lines 115-118 from Core/Controller/Installer.php:
if ('TRUE' === $this->request->query('phpinfo', '')) {
phpinfo();
return;
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | facturascripts/facturascripts | ≥ 2026 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facturascripts/facturascripts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of facturascripts/facturascripts has shipped for GHSA-vrxf-vrc4-22p7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vrxf-vrc4-22p7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vrxf-vrc4-22p7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vrxf-vrc4-22p7 in your dependencies?
O3 detects GHSA-vrxf-vrc4-22p7 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.