Security readout for executives and security teams
Plain-English summary
CVE-2026-3133 is a SQL injection in the login function of itsourcecode Document Management System 1.0. An unauthenticated remote attacker may be able to affect confidentiality, integrity, and availability of the underlying database. Public exploit information is reported, but CISA KEV listing is not indicated in the provided sources.
Executive priority
Treat as a near-term priority if the product is internet-facing or handles sensitive documents. Public exploit disclosure and unauthenticated remote reachability raise business risk. If the system is not deployed, no action is needed beyond asset confirmation.
Technical view
The issue affects /loging.php in the Login component. Manipulating the Username argument can lead to SQL injection. The provided CVSS v2 score is 7.5, with network access, low complexity, and no authentication required. CWE mappings include CWE-89 and CWE-74. Affected product evidence is limited to itsourcecode Document Management System version 1.0.
Likely exposure
Risk is highest for organizations running itsourcecode Document Management System 1.0 where the login page is reachable from untrusted networks. Exposure cannot be assumed for other versions or products based on the provided sources.
Exploitation context
The source bundle states remote exploitation is possible and that an exploit has been publicly disclosed. There is no provided evidence of active exploitation in the wild or inclusion in CISA KEV.
Researcher notes
Evidence is based on CVE/VulDB-style reporting and a GitHub issue reference. The affected processing is described as unknown beyond /loging.php Username handling. No official patch, workaround, or vendor advisory is included in the provided source bundle.
Mitigation direction
- Identify whether itsourcecode Document Management System 1.0 is deployed.
- Restrict external access to the login page where business operations allow.
- Check itsourcecode and VulDB references for vendor guidance or updates.
- Prioritize migration or compensating controls if no vendor fix is available.
- Monitor database and application logs for suspicious login activity.
Validation and detection
- Confirm the deployed product name and version.
- Locate exposure of /loging.php from internal and external networks.
- Review application logs for unusual Username input patterns.
- Assess database account permissions used by the application.
- Track vendor or advisory updates for confirmed remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3133 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-347616 | itsourcecode Document Management System Login loging.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-347616 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #758323 | itsourcecode Document Management System V1.0 SQL InjectionCVE reference · third-party-advisory
- https://github.com/ltranquility/CVE/issues/41CVE reference · exploit, issue-tracking
- https://itsourcecode.com/CVE reference · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.