CVE-2019-25159 is a SQL injection in config/cargos.php of mpedraza2020 Intranet del Monterroso up to 4.50.0, through the dni_profe argument. NVD scores it 5.5 Medium. Upgrade to version 4.51.0, which contains the fix, and check any forks of the project you run.
What's affected
- Product: mpedraza2020 Intranet del Monterroso, an intranet web application.
- Affected: versions up to and including 4.50.0.
- Fixed: 4.51.0. The project's release page for v4.51.0 exists and the record names the patch as commit 678190be.
- Severity: NVD scores 5.5 Medium (AV:A/AC:L/PR:L/UI:N). The record's own description calls the issue critical. Both appear in the source.
- Weakness: CWE-89, SQL injection, in the dni_profe argument.
How to check if you're exposed
- Find out whether your organisation runs this project. Check forks and vendored copies as well.
- Look at the deployed version in the application or in the repository tag. Anything at or below 4.50.0 is affected.
- Search the code for config/cargos.php and check how it builds its database query from the dni_profe value.
- Review the web server and database logs for unusual queries involving that parameter.
What to do now
- Upgrade to 4.51.0 or later, or apply commit 678190be to your fork.
- Move database access in this application to parameterised queries wherever user input is part of a query, not only in the one file.
- Limit the database account the application uses to the permissions it needs.
- If the application faces the internet, consider limiting access to the intranet network it is named for.
Why it matters
SQL injection happens when user input is placed in a query as text, so that input can change the meaning of the query. The record says the dni_profe argument in config/cargos.php leads to this. The fix lives in the project's commit and release.
The scoring is notable: the vector is adjacent network with low privileges, which gives the Medium number, while the description text calls it critical. Intranet applications are often assumed to be safe because of where they sit, and that assumption deserves a second look. The KEV flag is false and no exploitation is reported.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why are there two severity words in one record?
The score is 5.5, which is Medium. The description text says critical. Report both and describe the exposure honestly.
Will a web application firewall fix this?
It can block some patterns, but the reliable fix is to build queries with bound parameters, which is what upgrading achieves for this file.
Sources
- Release v4.51.0 on GitHub: Confirms the fixed release tag.
Last reviewed: 19 October 2026.