VYPR
High severity8.2NVD Advisory· Published Jun 1, 2026

CVE-2026-49491

CVE-2026-49491

Description

Pixa Bank 2.0 has an SQL injection vulnerability in agence-ajax.php that allows unauthenticated attackers to extract sensitive user data.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Pixa Bank 2.0 has an SQL injection vulnerability in agence-ajax.php that allows unauthenticated attackers to extract sensitive user data.

Vulnerability

Pixa Bank 2.0 contains an SQL injection vulnerability within the agence-ajax.php endpoint. This vulnerability is triggered by injecting SQL code into the rib parameter. The affected versions are not explicitly stated, but the vulnerability is present in Pixa Bank 2.0 [2].

Exploitation

Unauthenticated attackers can exploit this vulnerability by sending POST requests to the agence-ajax.php endpoint. These requests must include UNION-based SQL payloads within the rib parameter to successfully inject malicious SQL code and extract data [2].

Impact

Successful exploitation allows attackers to extract sensitive user information from the database. This includes details such as user names, email addresses, and phone numbers. The scope of the compromise is limited to the data accessible via the SQL injection, and no elevated privileges are gained beyond data retrieval [2].

Mitigation

No specific patched version or release date for a fix has been disclosed in the available references. Users are advised to consult vendor advisories for updates on mitigation strategies or patches. It is not listed on the KEV catalog, and its End-of-Life status is unknown [1, 2].

AI Insight generated on Jun 2, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

3

News mentions

0

No linked articles in our index yet.