NeoRazorX facturascripts up to 2025.80 REST API ModelClass::getOrderBy sort sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in NeoRazorX facturascripts up to 2025.80 and classified as critical. The impacted element is the function ModelClass::getOrderBy of the component REST API. The manipulation of the argument sort leads to sql injection.
This vulnerability is uniquely identified as CVE-2026-25513. The attack is possible to be carried out remotely. No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in NeoRazorX facturascripts up to 2025.80 and classified as critical. This issue affects the function ModelClass::getOrderBy of the component REST API. The manipulation of the argument sort with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
FacturaScripts is open-source enterprise resource planning and accounting software. Prior to version 2025.81, FacturaScripts contains a critical SQL injection vulnerability in the REST API that allows authenticated API users to execute arbitrary SQL queries through the sort parameter. The vulnerability exists in the ModelClass::getOrderBy() method where user-supplied sorting parameters are directly concatenated into the SQL ORDER BY clause without validation or sanitization. This affects all API endpoints that support sorting functionality. This issue has been patched in version 2025.81.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-25513 since 02/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 2025.81 eliminates this vulnerability. Applying the patch 1b6cdfa9ee1bb3365ea4a4ad753452035a027605 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-6094). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 2025.0
- 2025.1
- 2025.2
- 2025.3
- 2025.4
- 2025.5
- 2025.6
- 2025.7
- 2025.8
- 2025.9
- 2025.10
- 2025.11
- 2025.12
- 2025.13
- 2025.14
- 2025.15
- 2025.16
- 2025.17
- 2025.18
- 2025.19
- 2025.20
- 2025.21
- 2025.22
- 2025.23
- 2025.24
- 2025.25
- 2025.26
- 2025.27
- 2025.28
- 2025.29
- 2025.30
- 2025.31
- 2025.32
- 2025.33
- 2025.34
- 2025.35
- 2025.36
- 2025.37
- 2025.38
- 2025.39
- 2025.40
- 2025.41
- 2025.42
- 2025.43
- 2025.44
- 2025.45
- 2025.46
- 2025.47
- 2025.48
- 2025.49
- 2025.50
- 2025.51
- 2025.52
- 2025.53
- 2025.54
- 2025.55
- 2025.56
- 2025.57
- 2025.58
- 2025.59
- 2025.60
- 2025.61
- 2025.62
- 2025.63
- 2025.64
- 2025.65
- 2025.66
- 2025.67
- 2025.68
- 2025.69
- 2025.70
- 2025.71
- 2025.72
- 2025.73
- 2025.74
- 2025.75
- 2025.76
- 2025.77
- 2025.78
- 2025.79
- 2025.80
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: facturascripts 2025.81
Patch: 1b6cdfa9ee1bb3365ea4a4ad753452035a027605
Timeline
02/02/2026 CVE reserved02/05/2026 Advisory disclosed
02/05/2026 VulDB entry created
02/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-cjfx-qhwm-hf99
Status: Confirmed
CVE: CVE-2026-25513 (🔒)
GCVE (CVE): GCVE-0-2026-25513
GCVE (VulDB): GCVE-100-344417
EUVD: 🔒
Entry
Created: 02/05/2026 07:39Updated: 02/23/2026 16:48
Changes: 02/05/2026 07:39 (72), 02/18/2026 00:31 (1), 02/23/2026 16:48 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.