Skip to main content
VulnerabilityPublished

CVE-2026-3069: itsourcecode Document Management System · SQL Injection

Affects itsourcecode Document Management SystemSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
itsourcecodeDocument Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

To mitigate CVE-2026-3069, organizations should first verify whether they are running itsourcecode Document Management System version 1.0 and specifically assess exposure of the /edtlbls.php endpoint. Immediate mitigation steps include implementing web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'field1' parameter. Input validation and sanitization should be enforced at the application level to reject or properly escape malicious inputs. If source code access is available, developers should apply parameterized queries or prepared statements to eliminate injection vectors. Network segmentation and restricting access to the document management system to trusted internal networks can reduce exposure. Monitoring logs for unusual database query patterns or errors related to SQL injection attempts is critical for early detection. Organizations should engage with the vendor for official patches or updates and apply them promptly once available. Until a patch is released, consider disabling or restricting access to the vulnerable functionality if feasible. Regular backups of the database should be maintained to enable recovery in case of data tampering or loss.

Description

A security vulnerability has been detected in itsourcecode Document Management System 1.0. Affected is an unknown function of the file /edtlbls.php. The manipulation of the argument field1 leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…