CVE-2026-27892VulnerabilityPublished 7 May 2026Updated 30 Oct 2026

facturascripts/facturascripts · FacturaScripts Vulnerable to Unstripped Image Metadata (EXIF) Leakage via Library Module File Upload/Download

Affects facturascripts/facturascriptsSource GCVE Database

Compare

Authoritative record:CVE-2026-27892· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026 when convenient.

Data as of 30 Oct 2026, 17:04 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2026

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade facturascripts/facturascripts to 2026.

Affected software

Product	Affected	Fixed in
Packagistfacturascripts/facturascripts	Affected <2026	Fixed in 2026

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in FacturaScripts version 2026 that addresses this vulnerability by presumably stripping or sanitizing image metadata. Users should upgrade to version 2026 or later to remediate this issue. Until patched, restrict Library module access to trusted users only and avoid uploading images containing sensitive metadata. No vendor advisory indicates that no action is required or that the issue is already mitigated.

Description

FacturaScripts, an open-source ERP application, has a sensitive information disclosure vulnerability in its Library module. The application does not strip EXIF or other embedded metadata from user-uploaded images before storing and serving them. This allows any authenticated user with access to the Library to download images containing metadata such as GPS coordinates, device details, timestamps, and personal comments, potentially exposing sensitive personal information like an employee's home address.

Impact

The vulnerability allows authenticated users with access to the Library module to obtain sensitive metadata embedded in images uploaded by other users. This can lead to disclosure of exact physical locations (via GPS coordinates), device fingerprinting, behavioral profiling through timestamps, and exposure of personal comments or notes. Such information leakage can compromise employee privacy and organizational confidentiality by revealing personal and operational details unintentionally embedded in images.

Summary

The vulnerability in FacturaScripts affects the Library module's image upload and download pipeline, where uploaded images retain embedded EXIF metadata. This metadata can include GPS location, device make and model, timestamps, user comments, thumbnails, and other personally identifiable information. Since the Library module allows persistent storage and direct download of images by any authenticated user with access, this creates a one-to-many exposure vector for sensitive data. The issue arises because the application fails to perform any server-side metadata sanitization during upload, storage, or delivery. The vulnerability is identified as CVE-2026-27892 with a CVSS 3.1 score of 6.5 (medium severity). A fix is available in version 2026.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-212Improper Removal of Sensitive Information Before Storage or Transfer (opens in a new tab)
Base weakness
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Requirements
Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP ASVS 4.0.3
V8.3.2 (opens in a new tab)
Attack patterns
Windows ::DATA Alternate Data Stream (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 17:04 UTC

WeaknessesCWE-200, CWE-212

Technical details

References

Community reviews

Related threats