CVE-2019-25707 | eBrigade ERP 4.5 pdf.php ID sql injection (Exploit 46117 / EDB-46117)

VDB-357008 · CVE-2019-25707 · EXPLOIT 46117 EBRIGADE ERP 4.5 PDF.PHP ID SQL INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.4 $0-$5k 2.84+ Summaryinfo A vulnerability categorized as critical has been discovered in eBrigade ERP 4.5. This vulnerability affects unknown code of the file pdf.php. Such manipulation of the argument ID leads to sql injection. This vulnerability is listed as CVE-2019-25707. The attack may be performed from remote. In addition, an exploit is available. Detailsinfo A vulnerability was found in eBrigade ERP 4.5 and classified as critical. Affected by this issue is an unknown functionality of the file pdf.php. The manipulation of the argument id 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. CVE summarizes: eBrigade ERP 4.5 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries by injecting malicious code through the 'id' parameter. Attackers can send GET requests to pdf.php with crafted SQL payloads in the 'id' parameter to extract sensitive database information including table names and schema details. The weakness was presented by Ihsan Sencan as 46117. The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2019-25707 since 04/12/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:pdf.php it is possible to find vulnerable targets with Google Hacking. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the vulnerability database at Exploit-DB (46117). Productinfo Type Enterprise Resource Planning Software Vendor eBrigade Name ERP Version 4.5 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.7 VulDB Meta Temp Score: 6.4 VulDB Base Score: 6.3 VulDB Temp Score: 5.7 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.1 CNA Vector (VulnCheck): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Sql injection CWE: CWE-89 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Google Hack: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/12/2026 Advisory disclosed 04/12/2026 +0 days CVE reserved 04/12/2026 +0 days VulDB entry created 04/12/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 46117 Researcher: Ihsan Sencan Status: Not defined CVE: CVE-2019-25707 (🔒) GCVE (CVE): GCVE-0-2019-25707 GCVE (VulDB): GCVE-100-357008 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/12/2026 16:24 Changes: 04/12/2026 16:24 (82) Complete: 🔍 Cache ID: 99:8A5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸