CVE-2026-10256: itsourcecode Content Management System SQL injection in save_comment.php

CVE-2026-10256 · Severity: medium · CVSS 6.3 · Published 2026-06-01

A vulnerability exists in the itsourcecode Content Management System, a platform used for managing website content. An attacker can exploit this flaw to interfere with the website's database, potentially leading to the theft of sensitive information, unauthorized modification of data, or disruption of service. This occurs through the comment submission feature, where malicious commands can be hidden within the 'Name' field.

Technologies: Itsourcecode Content Management System. Vendors: Itsourcecode.

Quick answers

Is CVE-2026-10256 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-10256 being exploited in the wild.
How severe is CVE-2026-10256?
Medium severity, with a CVSS score of 6.3, published 1 June 2026.
Which products and versions are affected?
Itsourcecode Content Management System 1.0.
Is there a fix for CVE-2026-10256?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10256 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-10256?
Check whether you run Itsourcecode Content Management System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A SQL injection vulnerability exists in itsourcecode Content Management System 1.0 within the /save_comment.php file. The root cause is the improper sanitization of the 'Name' POST parameter before it is used in a database query. A remote attacker can exploit this by submitting a specially crafted comment, allowing for time-based blind SQL injection. While some reports suggest authentication is required (PR:L), the original researcher claims no authentication is necessary to reach the vulnerable component. Successful exploitation can lead to unauthorized database access, data exfiltration, and potential system compromise. A public exploit (PoC) using sqlmap has been disclosed.

Affected products

  • itsourcecode Content Management System 1.0

Timeline

  • 2026-05-09: disclosed: Initial researcher disclosure on GitHub
  • 2026-06-01: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.