What is the CVSS score of CVE-2026-5828?

CVE-2026-5828 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-5828?

Yes, a public proof-of-concept exploit is available for CVE-2026-5828. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-5828?

Within 24 hours: Identify all instances of Simple IT Discussion Forum 1.0 in your environment and take the affected application offline or restrict network access to /functions/addcomment.php. Within 7 days: Implement Web Application Firewall (WAF) rules to block SQL injection patterns targeting the postid parameter, and deploy intrusion detection signatures for this CVE. Within 30 days: Either upgrade to a patched version if the vendor releases one, migrate to an alternative discussion forum platform with active security support, or evaluate compensating controls if continued use is unavoidable.

Simple It Discussion Forum CVE-2026-5828

EUVD-2026-20821 MEDIUM

SQL Injection (CWE-89)

2026-04-09 VulDB

PHP SQLi Simple It Discussion Forum Code Projects

5.5

CVSS 4.0 · Vendor: VulDB

View

Vulnerability Assessment

Weakness	CWE CWE-89 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. Sign in to read
Impact	CVSS 7.3 reflects moderate-to-high severity SQL injection in unauthenticated endpoint. Network-accessible /functions/addcomment.php accepts untrusted postid parameter without sanitization, enabling remote database compromise. Publicly available POC lowers exploitation friction. Legacy forum software with minimal patching likelihood elevates real-world impact for deployed instances.
Exploit ScenarioDerived	Attacker sends HTTP request to /functions/addcomment.php with SQL payload in postid parameter (e.g., postid=1' OR '1'='1). No authentication required. Backend executes injected SQL, exfiltrating data or modifying database content. Publicly available exploit code exists.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 – Apr 09, 2026

SQL injection in Simple IT Discussion Forum 1.0 allows unauthenticated remote attackers to extract, modify, or delete database records via crafted postid parameter in /functions/addcomment.php. Publicly available exploit code exists. CVSS 7.3 indicates network-accessible attack requiring no user interaction, achieving partial confidentiality, integrity, and availability impact. Vulnerability disclosed with proof-of-concept on GitHub.

RemediationAI

No vendor-released patch identified at time of analysis. Immediate mitigation requires disabling or removing /functions/addcomment.php functionality until security updates become available. Implement parameterized SQL queries (prepared statements) to eliminate injection vectors. Deploy web application firewall rules blocking SQL metacharacters in postid parameter. Monitor database activity logs for anomalous query patterns. Reference vulnerability disclosure: https://github.com/lonelyuan/vunls/issues/7 and https://vuldb.com/vuln/356275 for technical indicators. Organizations should evaluate migration to actively maintained forum software given absence of vendor security response.

Affected VersionsENISA

Simple IT Discussion Forum 1.0

Affected Packages

euvd simple_it_discussion_forum 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

CWE-89 SQL injection stems from insufficient input validation on postid parameter within addcomment.php. PHP application accepts unsanitized user-supplied data directly in SQL queries, enabling arbitrary SQL command execution. Network accessibility (AV:N) and low attack complexity (AC:L) combined with no authentication requirement (PR:N) create trivial exploitation conditions.

Know when Simple It Discussion Forum 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

Vendor (VulDB) PRIMARY 5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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

None

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

CVSS changed

Apr 29, 2026 - 01:11 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

PoC Detected

Apr 09, 2026 - 02:16 vuln.today

Public exploit code

CVE Published

Apr 09, 2026 - 01:00 nvd

MEDIUM 6.9

DescriptionCVE.org

A vulnerability was found in code-projects Simple IT Discussion Forum 1.0. The affected element is an unknown function of the file /functions/addcomment.php. The manipulation of the argument postid results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Executive ViewAI

Why It Matters

Simple IT Discussion Forum 1.0 contains an unauthenticated SQL injection vulnerability in its comment functionality that allows remote attackers to extract, modify, or delete database records without authentication. Organizations running this forum software face immediate risk of data theft, unauthorized modifications, and potential service disruption, with exploit code already publicly available. This vulnerability requires urgent mitigation given the lack of vendor patch availability.

Business Impact: High

Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: (1) Implement WAF rules to detect and block SQL injection attempts in the postid parameter; (2) Restrict network access to the forum application through firewall rules or IP allowlisting; (3) Deploy database activity monitoring to detect suspicious queries; (4) Apply database query parameterization at the application layer if source code modification is possible; (5) Maintain frequent encrypted backups to enable recovery from data manipulation or deletion.

Threat Intelligence Overview

EPSS Score

0.0%

Top 91% exploitable

Exploit

POC

Public exploit code exists

Social Media

Sightings

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 MEDIUM

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.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.