CVE-2026-49491
Deferred Deferred - Pending Action
SQL Injection in Pixa Bank 2.0 via agence-ajax.php

Publication date: 2026-06-01

Last updated on: 2026-06-01

Assigner: VulnCheck

Description
Pixa Bank 2.0 contains an SQL injection vulnerability that allows unauthenticated attackers to extract sensitive data by injecting SQL code into the 'rib' parameter. Attackers can send POST requests to the agence-ajax.php endpoint with UNION-based SQL payloads to retrieve user information including names, email addresses, and phone numbers from the database.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-01
Last Modified
2026-06-01
Generated
2026-06-22
AI Q&A
2026-06-02
EPSS Evaluated
2026-06-21
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
pixa_bank pixa_bank 2.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-49491 is an SQL injection vulnerability found in Pixa Bank 2.0. It allows unauthenticated attackers to inject malicious SQL code into the 'rib' parameter by sending specially crafted POST requests to the agence-ajax.php endpoint.

By exploiting this vulnerability, attackers can use UNION-based SQL payloads to extract sensitive user information such as names, email addresses, and phone numbers from the database.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive user data including personal identifiers like names, email addresses, and phone numbers.

Since the attack requires no authentication, it poses a high risk of data breach, potentially compromising user privacy and trust.

The CVSS v3.1 score of 8.2 indicates a high severity impact, emphasizing the critical nature of this vulnerability.

Compliance Impact

The vulnerability in Pixa Bank 2.0 allows unauthenticated attackers to extract sensitive user data such as names, email addresses, and phone numbers via SQL injection. This unauthorized access to personal data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personally identifiable information (PII) and sensitive health information.

Specifically, the exposure of such data could result in violations of GDPR's requirements for data confidentiality and integrity, potentially leading to legal penalties and reputational damage. Similarly, for HIPAA, if the data includes protected health information, this breach could constitute a violation of patient privacy rules.

Detection Guidance

This vulnerability can be detected by monitoring for unusual POST requests to the agence-ajax.php endpoint that include the 'rib' parameter with suspicious SQL injection payloads, especially UNION-based SQL code.

Network administrators can use tools like curl or wget to manually test the endpoint by sending crafted POST requests with SQL injection payloads in the 'rib' parameter to see if sensitive data is returned.

Example command to test the vulnerability using curl:

  • curl -X POST -d "rib=1' UNION SELECT name, email, phone FROM users--" https://targetsite.com/agence-ajax.php

Additionally, network intrusion detection systems (NIDS) can be configured to alert on POST requests containing SQL keywords such as UNION, SELECT, or typical SQL injection patterns targeting the 'rib' parameter.

Mitigation Strategies

Immediate mitigation steps include implementing input validation and sanitization on the 'rib' parameter to prevent SQL injection.

Use prepared statements or parameterized queries in the backend code handling the agence-ajax.php endpoint to avoid direct injection of user input into SQL queries.

Restrict access to the agence-ajax.php endpoint if possible, and monitor logs for suspicious activity.

Apply any available patches or updates from the vendor addressing this vulnerability.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49491. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart