CVE-2019-25507
SQL Injection in Ashop Shopping Cart Allows Data Extraction
Publication date: 2026-03-04
Last updated on: 2026-03-04
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ashop_software | ashop_shopping_cart_software | * |
| ashop | shopping_cart_software | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "This vulnerability is an SQL injection in the Ashop Shopping Cart Software. It occurs because the software does not properly sanitize the 'shop' parameter in GET requests to the index.php page. An attacker can inject malicious SQL code through this parameter, allowing them to manipulate database queries."}, {'type': 'paragraph', 'content': 'Specifically, attackers can use UNION-based SQL injection techniques to combine their own queries with legitimate ones, enabling them to extract sensitive information from the database without authentication.'}] [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive database information. Attackers exploiting this flaw can retrieve confidential data stored in the database, which may include user information, credentials, or other critical business data.
Because the vulnerability allows unauthenticated remote attackers to execute arbitrary SQL queries, it can compromise the integrity and confidentiality of the application’s data, potentially leading to further attacks or data breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by sending crafted GET requests to the vulnerable index.php page, specifically targeting the 'shop' parameter with SQL injection payloads."}, {'type': 'paragraph', 'content': 'A typical detection command involves using curl or a similar HTTP client to send a request with a UNION-based SQL injection payload to observe if the response contains injected data.'}, {'type': 'list_item', 'content': 'Example curl command to test the vulnerability: curl "http://[target]/index.php?cat=1&exp=&shop=-5438\') UNION ALL SELECT CONCAT(0x71786b6a71,0x6357557777645143654a726369774c4167665278634a46617758614d66506b46434f4b7669565054,0x716a787671),NULL-- fmIb"'}, {'type': 'paragraph', 'content': 'If the response contains the concatenated hexadecimal string decoded, it indicates the presence of the SQL injection vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
I don't know