CVE-2023-54359
Time-Based Blind SQL Injection in Adivaha Travel Plugin
Publication date: 2026-04-09
Last updated on: 2026-04-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| adivaha | travel_plugin | 2.3 |
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?
The WordPress adivaha Travel Plugin version 2.3 contains a time-based blind SQL injection vulnerability. This means that unauthenticated attackers can manipulate database queries by injecting SQL code through the 'pid' GET parameter. Specifically, attackers send crafted requests to the /mobile-app/v3/ endpoint using XOR-based payloads in the 'pid' parameter to extract sensitive information from the database or cause a denial of service.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized extraction of sensitive database information, which could lead to data breaches. Additionally, attackers can cause denial of service by exploiting the vulnerability, potentially making the affected service unavailable to legitimate users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP requests to the /mobile-app/v3/ endpoint with specially designed 'pid' GET parameter values that attempt to trigger the time-based blind SQL injection. Monitoring for unusual or suspicious requests targeting this endpoint with XOR-based payloads can help identify exploitation attempts.
For detection, you can use tools like curl or specialized web vulnerability scanners to send test requests. An example curl command to test might be:
- curl -i "http://<target>/mobile-app/v3/?pid=1' XOR SLEEP(5)--"
If the response time is significantly delayed, it may indicate the presence of the SQL injection vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Apply any available patches or updates for the adivaha Travel Plugin to a version that fixes this vulnerability.
- If patches are not available, consider disabling or restricting access to the /mobile-app/v3/ endpoint to prevent exploitation.
- Implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'pid' parameter.
- Review and harden database permissions to limit the impact of any successful injection.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the WordPress adivaha Travel Plugin 2.3 is a time-based blind SQL injection that allows unauthenticated attackers to extract sensitive database information. This exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.
By enabling attackers to manipulate database queries and potentially access or leak sensitive data, this vulnerability increases the risk of data breaches, which can result in violations of these standards and regulations.