CVE-2026-81673: Multiple Vulnerabilities in TOOOLS' iSquad
The ‘/ws/apitribuna/setVisita’ endpoint is vulnerable to SQL injection through the id_video and id_ambito parameters. The application does not validate or sanitize these inputs before including them in SQL queries. This allows a remote attacker to inject SQL syntax and disrupt the execution of queries, causing database errors and potentially manipulating visit tracking records. Given the nature of the endpoint, this could also affect the integrity of analytics and the accuracy of records.
Security readout for executives and security teams
Plain-English summary
TOOOLS iSquad contains a remotely reachable database injection flaw in a visit-tracking endpoint. An unauthenticated attacker could potentially alter records, expose database information, or disrupt service. Analytics and record accuracy may also be compromised. Exposure depends on whether the affected endpoint is deployed and accessible.
Executive priority
Treat this as an immediate priority wherever iSquad is deployed or possibly exposed. First establish endpoint reachability, then contain public access and apply vendor-supported remediation. Consider incident investigation if suspicious database errors, requests, or analytics changes are found.
Technical view
The `/ws/apitribuna/setVisita` endpoint inserts the `id_video` and `id_ambito` parameters into SQL queries without adequate validation or sanitization. The CVSS 4.0 assessment is 9.3, with network access, low complexity, no authentication, no user interaction, and high confidentiality, integrity, and availability impacts.
Likely exposure
Highest risk applies to iSquad deployments where the affected web-service endpoint is reachable from untrusted networks. The supplied version metadata lists version “0” and a default status of unaffected, making exact product-version applicability unclear. Organizations should confirm exposure directly with TOOOLS or INCIBE guidance.
Exploitation context
The sources do not report active exploitation, and CVE-2026-81673 is not identified as a KEV entry in the supplied bundle. Nevertheless, unauthenticated, low-complexity, network-accessible SQL injection is inherently attractive to attackers. No public exploit details should be required to prioritize remediation.
Researcher notes
CWE-89 and the CVSS vector support a critical unauthenticated SQL-injection assessment. However, the supplied bundle does not identify a fixed version, detailed patch, or confirmed exploitation. The affected-version value “0” and default-unaffected status create applicability uncertainty that requires vendor confirmation.
Mitigation direction
Review and apply the remediation specified by TOOOLS or the INCIBE advisory.
Restrict the affected endpoint to trusted networks until remediation is confirmed.
Use application-layer filtering as temporary defense, without treating it as a permanent fix.
Ensure database permissions available to iSquad follow least-privilege principles.
Back up relevant data before remediation and preserve logs for investigation.
Validation and detection
Inventory iSquad deployments and determine whether the affected endpoint is reachable externally.
Confirm installed versions and remediation status with TOOOLS or INCIBE guidance.
Review web and database logs for unusual requests, errors, or record changes.
Check visit-tracking records and analytics for unexplained manipulation or inconsistencies.
Perform authorized, non-destructive verification after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.