What is the CVSS score of CVE-2025-6122?

CVE-2025-6122 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: 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. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2025-6122?

Yes, a public proof-of-concept exploit is available for CVE-2025-6122. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-6122?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Restaurant Order System CVE-2025-6122

EUVD-2025-18395 LOW

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)

2025-06-16 cna@vuldb.com

PHP SQLi Restaurant Order System Fabian

2.1

CVSS 4.0 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate to application
Delivery

Send crafted request to /table.php with malicious ID parameter
Exploit

SQL injection executes
Execution

Extract or modify database data
Impact

Impact on confidentiality/integrity

Vulnerability Assessment

Weakness	CWE CWE-74 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Input neutralization, injection prevention
Exploitation Conditions	The attacker must have low-privileged access to the application (PR:L from CVSS). The vulnerability is in the /table.php endpoint, which requires authentication. No special configuration is needed beyond default installation.
Impact	CVSS 4.0 base score is 2.1 (Low) with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N, indicating low impact on confidentiality, integrity, and availability. The attack requires low privileges (PR:L) but no user interaction. EPSS score is 0.09% (percentile 26%), suggesting low exploitation probability. A public POC exists, but no CISA KEV listing. SSVC decision: exploitation status 'PoC', automatable likely yes, technical impact low. Overall, this is a low-risk issue despite the critical classification in the description.
Exploit ScenarioDerived	An attacker with low-privileged access to the Restaurant Order System sends a crafted HTTP request to /table.php with a malicious ID parameter. The SQL injection allows the attacker to extract sensitive data from the database, such as user credentials or order information. A public POC is available on GitHub.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).

No patch listed yet 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv2 – Jul 26, 2026

SQL injection in code-projects Restaurant Order System 1.0 allows remote authenticated attackers to manipulate database queries via the ID parameter in /table.php. A public exploit exists, but no active exploitation has been confirmed. EPSS score is low (0.09%), indicating limited exploitation likelihood.

Earlier versions of this analysis (1)

v1 Mar 14, 2026 - 21:59 CVSS 6.3

RemediationAI

Upgrade to a patched version if available; otherwise, apply input validation and parameterized queries for the ID parameter in /table.php. As a workaround, restrict access to /table.php to trusted users only. No official patch has been identified from the vendor.

Affected VersionsENISA

Restaurant Order System 1.0

Affected Packages

euvd restaurant_order_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 is a SQL injection (CWE-74) in a PHP-based restaurant order management system. The affected component is /table.php, which processes the ID parameter without proper sanitization. The CPE indicates the product is 'Restaurant Order System' version 1.0 by Fabian. SQL injection allows an attacker to inject arbitrary SQL commands into the database query, potentially leading to data exfiltration or modification.

Know when Restaurant Order 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD 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

vuln.today AI 5.4 MEDIUM

PR:L due to required authentication; C:L/I:L/A:N per low impact.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

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

Severity Changed

Apr 29, 2026 - 01:11 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

6.3 (MEDIUM) 2.1 (LOW)

PoC Detected

Jun 24, 2025 - 20:14 vuln.today

Public exploit code

CVE Published

Jun 16, 2025 - 13:15 nvd

MEDIUM 6.3

CVE Published

Jun 16, 2025 - 13:15 cve.org

LOW 2.1

DescriptionCVE.org

A vulnerability, which was classified as critical, was found in code-projects Restaurant Order System 1.0. This affects an unknown part of the file /table.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Executive ViewAI

Why It Matters

CVE-2025-6122 presents moderate security risk, a injection vulnerability rated CVSS 6.3. Exploitation could allow attackers to execute code or inject malicious input. Proof-of-concept code is publicly available. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low

Compensating Controls

Apply vendor patch. If patching is delayed: deploy WAF rules, restrict network access, enable logging.

Threat Intelligence Overview

EPSS Score

0.1%

Top 74% exploitable

Prevalence

Low

niche product, limited deployment

Exploit

POC

Public exploit code exists

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

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.1%

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.