dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-42878

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FacturaScripts is an open source accounting and invoicing software. Prior to v2026, 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. This vulnerability is fixed in v2026.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated information disclosure vulnerability in the Installer controller of FacturaScripts allows remote attackers to trigger phpinfo() by requesting /?phpinfo=TRUE on fresh deployments, exposing full PHP configuration, server environment variables (including database credentials, API keys, and application secrets), filesystem paths, and loaded extensions without authentication.

MitigationUpgrade to FacturaScripts v2026 or later to eliminate the vulnerable installer endpoint. For deployed systems, ensure the /installer path is removed or access-controlled in production and rotate any credentials that may have been exposed via environment variables.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if installer endpoint is accessible
    Request http(s)://<your-host>/?phpinfo=TRUE and check if the response contains a full phpinfo() output page
    Affected if The page loads and displays PHP version, configuration details, and environment variables without requiring authentication
  2. Check for existence of installer directory
    Inspect the web root directory for an 'installer' folder or any directory related to FacturaScripts installation that may remain after initial setup
    Affected if The installer directory or installation files are present on the production server
  3. Confirm FacturaScripts version
    Locate the version file or bootstrap file in the FacturaScripts installation and read the version number (typically in a version.php, constants.php, or similar file in the root or config directory)
    Affected if The installed version is below v2026 (e.g., any v20xx or earlier release)
  4. Test for unauthenticated access to installer routes
    Attempt to access common installer paths such as /installer, /install, or /setup without providing any credentials
    Affected if These paths are accessible and return installation or configuration pages without authentication

You are affected if the installer remains accessible, /?phpinfo=TRUE returns PHP configuration data without authentication, or the installed FacturaScripts version is below v2026.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FacturaScripts v2026 or later to eliminate the vulnerable installer endpoint. For deployed systems, ensure the /installer path is removed or access-controlled in production and rotate any credentials that may have been exposed via environment variables.

Recommended fix High confidence

v2026

  1. 1. Back up your current FacturaScripts installation and database before proceeding with any upgrade.
  2. 2. Download FacturaScripts v2026 from the official repository (github.com/facturascripts/facturascripts) or use the built-in update mechanism if available.
  3. 3. Replace the existing FacturaScripts files with the v2026 files, preserving your configuration and data directories as instructed in the upgrade documentation.
  4. 4. After upgrading, verify the vulnerability is patched by attempting to access /?phpinfo=TRUE - it should not return phpinfo() output.
  5. 5. Ensure your application is functioning normally after the upgrade.
Caveat Standard upgrade considerations apply - review release notes for any configuration or feature changes between your current version and v2026

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42878 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42878 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data