FacturaScripts is open-source enterprise resource planning and accounting software. Prior to 2025.8, there a reflected XSS bug in FacturaScripts. The problem is in how error messages get displayed. Twig's | raw filter is used, which skips HTML escaping. When triggering a database error (like passing a string where an integer is expected), the error message includes the input and gets rendered without sanitization. This vulnerability is fixed in 2025.8.

Affected: Packagist: facturascripts/facturascripts

# Reflected XSS via SQL Error Messages

## Summary

A reflected XSS bug has been found in FacturaScripts. The problem is in how error messages get displayed - it's using Twig's `| raw` filter which skips HTML escaping. When a database error is triggered (like passing a string where an integer is expected), the error message includes all input and gets rendered without sanitization.

Attackers can use this to phish credentials from other users since HttpOnly is set on cookies (so stealing cookies directly won't work, but attackers can inject a fake login form).

**CVSS 6.1 (Medium-High)**

---

## What was Found

### Where the bug exists in the code:

`Core/View/Macro/Utils.html.twig`, line 27:

```twig {% for item in messages %} <div>{{ item.message | raw }}</div> {% endfor %} ```

That `| raw` is the problem. It tells Twig not to escape anything.

### How it works

So here's what happens:

1. Hhit `/EditProducto?code=<svg onload=alert(1)> or <img src=x onerror=alert(1)>` 2. The app tries to look up a product with that "code" 3. PostgreSQL throws an error because `<svg onload=alert(1)>` isn't a valid integer 4. The error goes something like: ``` ERROR: invalid input syntax for type integer: "<svg onload=alert(1)>" LINE 1: SELECT * FROM "productos" WHERE "idproducto" = '<img src=x onerror=alert(1)>" ``` 5. This gets logged via MiniLog and displayed to the user 6. Because of `| raw`, the browser actually executes the JS

The error logging happens in `Core/Base/D…