Security readout for executives and security teams
Plain-English summary
A backend reporting feature in smart-web2 v1.3.1 can reportedly let a remote, unauthenticated attacker submit database instructions. Successful abuse could expose, alter, or destroy sensitive data and disrupt service. The issue is rated critical, but the supplied sources do not document active exploitation or a confirmed vendor fix.
Executive priority
Prioritize immediate exposure assessment and containment. An unauthenticated, network-reachable SQL injection with potential full database impact warrants urgent action. Escalate internet-accessible instances first, while recognizing that the supplied sources do not identify active exploitation or a confirmed patch.
Technical view
ReportController.save() stores the sqlResource.sql value in t_report_sql_resource. The value is later inserted directly into Hibernate native queries without parameterization or filtering, creating CWE-89 SQL injection. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Highest risk applies to internet-accessible smart-web2 v1.3.1 deployments where the report backend and ReportController.save() interface are reachable. Formal vendor, CPE, deployment defaults, and other affected versions are not identified, so asset ownership and broader exposure remain uncertain.
Exploitation context
The CVSS vector indicates remote, unauthenticated exploitation with low complexity and no user interaction. However, the supplied record is not in KEV, and no cited source confirms exploitation in the wild. Treat technical exploitability as serious without claiming active attacks.
Researcher notes
The central data flow is user-controlled sqlResource.sql persisted through ReportController.save(), then consumed by Hibernate native queries. Important unknowns include endpoint routing, authentication enforcement, default exposure, database privileges, execution timing, supported fixed versions, and whether other releases share the vulnerable path. Validate defensively without testing production systems destructively.
Mitigation direction
- Identify and isolate any smart-web2 v1.3.1 deployments, especially internet-accessible report interfaces.
- Restrict report-backend access to trusted administrators and networks as an interim control.
- Check project or vendor guidance for an official patch or supported remediation.
- Replace direct SQL embedding with parameterized queries and strict server-side input controls.
- Protect database credentials using least privilege to limit potential impact.
Validation and detection
- Inventory deployed smart-web2 versions and confirm whether v1.3.1 is present.
- Determine whether ReportController.save() is reachable without authentication from untrusted networks.
- Review application code for direct sqlResource.sql insertion into Hibernate native queries.
- Inspect relevant application, database, and proxy logs for unusual report-query activity.
- Confirm any remediation parameterizes queries and prevents user-controlled SQL execution.
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-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 lookupCVE-2026-75334 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fangtang7/CVE/blob/main/smart-web2/smart-web2%20v1.3.1%20SQL%20Injection.mdCVE reference, mitre
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 used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.