CVE-2022-26171: Bank Management System v1.o was discovered to contain a SQL injection vulnerability via the email parameter.

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-26171 is a critical-severity flaw (CVSS 9.8) affecting bank management system. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Bank Management System v1.o was discovered to contain a SQL injection vulnerability via the email parameter.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 30%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-03-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: bank management system project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-03-02 23:15 UTCPublished CVE record published
2026-06-17 04:34 UTCUpdated Record last modified

bank management system project bank management system DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy bank-management-system || rpm -q bank-management-system || bank-management-system --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison bank-management-system sudo apt install bank-management-system=<VERSION_BEFORE_1.0> sudo apt-mark hold bank-management-system

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list bank-management-system sudo dnf downgrade bank-management-system-<VERSION_BEFORE_1.0> sudo dnf versionlock add bank-management-system

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-26171?

bank management system: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-26171 being exploited?

CVE-2022-26171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-26171 affect?

CVE-2022-26171 affects bank management system. Severity is critical (CVSS 9.8). Bank Management System v1.o was discovered to contain a SQL injection vulnerability via the email parameter.

How urgent is CVE-2022-26171?

Priority 62/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-2087 LOW 3.5 DOWNGRADE A vulnerability, which was classified as problematic, was found in SourceCodester Bank Management System 1.0
CVE-2022-2086 MEDIUM 6.3 DOWNGRADE A vulnerability, which was classified as critical, has been found in SourceCodester Bank Management System 1.0

References

← Back to latest CVEs