Skip to main content
VulnerabilityPublished Updated

CVE-2023-50743: Kashipara Group Online Notice Board System · SQL Injection

Affects Kashipara Group Online Notice Board SystemSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Kashipara Group Online Notice Board SystemAffected
  • =1.0
Fixed in–

AI-suggested

Immediate mitigation steps include implementing robust input validation and sanitization on the 'dd' parameter within registration.php to ensure that only expected, safe characters are accepted. Employing parameterized queries or prepared statements in the database access layer will effectively prevent SQL Injection by separating code from data. Organizations should conduct a thorough code review of the entire application to identify and remediate any other injection points. In the absence of an official patch, deploying a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL Injection attempts targeting the vulnerable parameter can provide temporary protection. Network segmentation and restricting access to the notice board system to trusted internal users or VPN-only access can reduce exposure. Monitoring logs for suspicious database errors or anomalous query patterns is recommended to detect potential exploitation attempts early. Finally, organizations should engage with the vendor to request an official patch or upgrade path and plan for timely application once available.

Description

Online Notice Board System v1.0 is vulnerable to multiple Unauthenticated SQL Injection vulnerabilities. The 'dd' parameter of the registration.php resource does not validate the characters received and they are sent unfiltered to the database.

References

Community reviews

Loading reviews…