Skip to main content

Simple Gym Management System CVE-2026-5206

| EUVDEUVD-2026-17577 LOW
SQL Injection (CWE-89)
2026-03-31 VulDB
2.1
CVSS 4.0 · Vendor: VulDB
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This vulnerability presents a moderate real-world risk despite the low CVSS score of 5.3. The authentication requirement (PR:L) reduces immediate exposure compared to unauthenticated SQL injection, as attackers must first obtain valid credentials or compromise an existing user account. However, the CVSS v4.0 vector E:P field indicates proof-of-concept code is publicly available, increasing practical exploitation likelihood. The vulnerability affects a niche gym management application with likely limited user base, reducing the attack surface compared to mainstream software. SSVC framework considerations: exploitation is confirmed (POC available), but automation feasibility depends on authentication mechanism strength; technical impact is limited but could expose payment records, customer PII, or allow unauthorized transaction modification. Priority should reflect the authentication barrier and application scope, but the public exploit availability warrants prioritization for organizations running this software.

Exploit ScenarioDerived

An authenticated user of Simple Gym Management System (e.g., gym staff or customer with login credentials) submits a crafted SQL injection payload in the Payment_id or customer_id parameter when processing a payment transaction. The unvalidated input is directly concatenated into a SQL query, allowing the attacker to manipulate query logic-for example, injecting 'OR 1=1' to bypass payment authorization checks, retrieve all customer payment records, or modify transaction amounts in the database. Publicly available exploit code from the referenced GitHub issue simplifies weaponization for attackers with basic technical knowledge.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 31, 2026

SQL injection in code-projects Simple Gym Management System 1.0 Payment Handler allows authenticated remote attackers to manipulate Payment_id, Amount, customer_id, payment_type, and customer_name parameters to execute arbitrary SQL queries, potentially leading to unauthorized data access or modification. Publicly available exploit code exists for this vulnerability; patch status from vendor remains unconfirmed.

RemediationAI

Organizations running Simple Gym Management System 1.0 should contact code-projects directly via https://code-projects.org/ to obtain a patched version addressing the SQL injection in the Payment Handler component. No specific vendor-released patch version was confirmed in available data at time of analysis. As an interim measure, restrict access to the Payment Handler component through network or application-level controls, limiting exposure to authenticated users only. Additionally, implement Web Application Firewall (WAF) rules to detect and block SQL injection syntax in payment parameters (Payment_id, Amount, customer_id, payment_type, customer_name). Database access should be configured with least-privilege principles, and input validation filters should be applied at the application level pending a vendor patch.

Affected VersionsENISA

Simple Gym Management System 1.0

Affected Packages

euvd simple_gym_management_system no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from improper input validation and parameterization in the Payment Handler component of Simple Gym Management System, classified as CWE-89 (SQL Injection). The application fails to sanitize or use prepared statements for user-supplied input in payment-related parameters, allowing attackers to inject malicious SQL syntax. The CVSS v4.0 vector indicates the attack requires network access (AV:N), low complexity (AC:L), and authenticated login (PR:L), suggesting the Payment Handler is accessible to logged-in users without special privileges. The exploitation probability (E:P) is marked as Proof of Concept available, and the impact is limited to low confidentiality, integrity, and availability within the application context (VC:L/VI:L/VA:L).

Know when Simple Gym Management System gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

4
Severity Changed
Apr 29, 2026 - 01:11 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:11 NVD
5.3 (MEDIUM) 2.1 (LOW)
PoC Detected
Apr 01, 2026 - 14:23 vuln.today
Public exploit code
CVE Published
Mar 31, 2026 - 17:30 nvd
MEDIUM 5.3

DescriptionCVE.org

A security vulnerability has been detected in code-projects Simple Gym Management System 1.0. This vulnerability affects unknown code of the component Payment Handler. The manipulation of the argument Payment_id/Amount/customer_id/payment_type/customer_name leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy