Skip to main content
Menu
CVEs

Banking Management System SQL injection in manage_request.php

CVE-2026-134569Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

The itsourcecode Banking Management System has an SQL injection flaw in the ID argument of its manage_request.php file. An attacker can exploit it remotely over the network with low-level login access.

Written by a model

Original description

A vulnerability has been found in itsourcecode Banking Management System 1.0. This impacts an unknown function of the file /manage_request.php. Such manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134569 (itsourcecode Banking Management System manage_request.php sql injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134569 (entry last updated 2026-11-22):
Affected:
- itsourcecode Banking Management System: versions 1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-134569 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134569 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/441693
- https://vuldb.com/vuln/441693/cti
- https://vuldb.com/cve/CVE-2026-134569
- https://vuldb.com/submit/1053567
- https://itsourcecode.com/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134569
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134569"}.

Affected versions

cve.now Index

13Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkitsourcecode.com · itsourcecode.com
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134569
RecordNVD · CVE-2026-134569
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · ZacheryZ/submit · Issue #4
Other links 4
AdvisoryVulDB · Advisory #441693
AdvisoryVulDB · Threat intelligence #441693
AdvisoryVulDB · CVE-2026-134569 record
AdvisoryVulDB · Submission #1053567

Questions about CVE-2026-134569

Is CVE-2026-134569 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-134569?

Banking Management System: version 1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.