CVE-2019-25503
SQL Injection in PHPads 2.0 click.php3 Exposes Database
Publication date: 2026-03-04
Last updated on: 2026-03-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| blondish | phpads | 2.0 |
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': "The vulnerability in PHPads 2.0 is an SQL injection flaw found in the 'click.php3' script via the 'bannerID' parameter. This allows unauthenticated attackers to inject arbitrary SQL commands by manipulating the 'bannerID' value in the URL."}, {'type': 'paragraph', 'content': "The application uses the deprecated 'ereg' function without proper input sanitization to process the 'bannerID' parameter, enabling attackers to craft malicious SQL queries."}, {'type': 'paragraph', 'content': "An attacker can exploit this by injecting SQL code that uses functions like 'extractvalue' combined with 'concat' and 'select database()' to extract sensitive information such as the current database name."}] [1]
How can this vulnerability impact me? :
This SQL injection vulnerability can lead to unauthorized access to the database, allowing attackers to extract sensitive information.
Attackers can manipulate SQL queries executed by the application, potentially leading to data leakage or further compromise of the system.
Since the vulnerability is exploitable without authentication, it poses a high risk to the confidentiality and integrity of the data managed by the application.
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 vulnerability can be detected by identifying instances of the PHPads 2.0 application that use the vulnerable \'click.php3\' script with the \'bannerID\' parameter. One method is to use Google dork queries such as inurl:"click.php3?bannerID=" to locate potentially vulnerable URLs.'}, {'type': 'paragraph', 'content': "To test for the SQL injection, you can attempt to inject a crafted payload into the 'bannerID' parameter that uses MySQL functions like extractvalue to see if the application returns database error messages or extracts database information."}, {'type': 'paragraph', 'content': 'An example of a proof-of-concept URL to test the vulnerability is:'}, {'type': 'list_item', 'content': 'http://server/phpads/click.php3?bannerID=-1/*!50000and*/+/*!50000extractvalue*/(0x0a,/*!50000concat*/(0x0a,0x73337830753a,(/*!50000select*/%20database()),0x3a7333783075))--+-'}, {'type': 'paragraph', 'content': 'If the application responds with database error messages or reveals the current database name, it indicates the presence of the SQL injection vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
I don't know