PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-92526 itsourcecode CVE debrief

A SQL injection vulnerability has been identified in the Itsourcecode Leave Management System 1.0, specifically in the /module/leave/index.php file. The vulnerability is exploitable remotely and has been publicly disclosed. This vulnerability may impact remote access vectors, and defenders should assess exposure and prioritize patching or mitigation efforts accordingly. The vulnerability has a CVSS score of 2.1 and is considered LOW severity. The exploit has been publicly disclosed and may be used.

Vendor
itsourcecode
Product
Leave Management System
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-22
Advisory published
2026-09-16
Advisory updated
2026-09-22

Who should care

Defenders responsible for the Itsourcecode Leave Management System 1.0 should assess exposure and prioritize patching or mitigation efforts. This vulnerability may impact remote access vectors, and operators, platforms, vulnerability-management, and security teams should review affected scope, severity, and vendor guidance.

Why it matters

CVE-2026-92526 is a SQL injection vulnerability in the Itsourcecode Leave Management System 1.0. Defenders should assess exposure, prioritize patching, and monitor for potential exploitation attempts.

  • Verify remote access exposure and potential exploitation
  • Assess patching priority for the Itsourcecode Leave Management System 1.0
  • Monitor for potential SQL injection attempts

Technical summary

The Itsourcecode Leave Management System 1.0 is vulnerable to SQL injection via the /module/leave/index.php file. The vulnerability has a CVSS score of 2.1 and is considered LOW severity. The exploit has been publicly disclosed and may be used. Defenders should assess exposure and prioritize patching for the Itsourcecode Leave Management System 1.0, particularly for remote access vectors. The vulnerability affects the Itsourcecode Leave Management System 1.0, and its defensive impact should be reviewed without unsupported root-cause or exploit claims.

Defensive priority

Assess exposure and prioritize patching for the Itsourcecode Leave Management System 1.0, particularly for remote access vectors.

Recommended defensive actions

  • Assess exposure of the Itsourcecode Leave Management System 1.0 in your environment
  • Prioritize patching or mitigating the SQL injection vulnerability
  • Monitor for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 2.1 and severity of LOW. However, specific details on affected versions and remediation are limited. Defenders should verify remote access exposure and potential exploitation attempts. The vulnerability affects the Itsourcecode Leave Management System 1.0, and its source-confidence limits should be reviewed.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-92526 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-92526

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-92526 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92526

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.