dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-49491

HIGH · 8.2 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Pixa Bank 2.0 has an unauthenticated SQL injection vulnerability in the 'rib' parameter at the agencia-ajax.php endpoint. Attackers can send crafted POST requests with UNION-based SQL payloads to extract sensitive user data including names, email addresses, and phone numbers from the database.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user input, particularly the 'rib' parameter. Input validation and proper output encoding should also be applied as defense-in-depth measures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Pixa Bank 2.0 installation
    Search web server directories for 'Pixa Bank' or 'pixa' folders, or look for files containing 'agencia-ajax.php'. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Use 'find / -name "agencia-ajax.php"' on Linux or search utilities on Windows.
    Affected if The application files are found on the server, indicating Pixa Bank 2.0 is installed.
  2. Verify vulnerable endpoint exists
    Check if agencia-ajax.php exists in the web-accessible directory. Confirm the file contains handling for a 'rib' parameter by inspecting the source code or attempting a HEAD request to the endpoint.
    Affected if The file agencia-ajax.php exists and processes a 'rib' parameter.
  3. Check application version
    Look for version information in the application: check README files, version.php, config files, or the main index page footer. Search the codebase for version strings like '2.0' or 'version' declarations.
    Affected if The installed version matches Pixa Bank 2.0 or cannot be determined (assume affected).
  4. Inspect 'rib' parameter handling
    Review agencia-ajax.php source code to verify if the 'rib' parameter is used in direct SQL queries without parameterized queries or prepared statements. Search for SQL keywords (SELECT, INSERT, UPDATE) concatenated with the 'rib' parameter.
    Affected if The 'rib' parameter is used in SQL queries without proper sanitization or prepared statements.
  5. Review access logs for exploitation attempts
    Search web server access logs (access.log, error.log) for POST requests to agencia-ajax.php containing 'rib' parameter. Look for UNION-based SQL injection patterns, common keywords: UNION, SELECT, FROM, WHERE in the request body.
    Affected if Suspicious POST requests with SQL injection patterns in the 'rib' parameter are found in logs.

If Pixa Bank 2.0 is installed and the agencia-ajax.php endpoint with an unvalidated 'rib' parameter is accessible, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations involving user input, particularly the 'rib' parameter. Input validation and proper output encoding should also be applied as defense-in-depth measures.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49491 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data