CVE-2026-81675: Multiple Vulnerabilities in TOOOLS' iSquad
The endpoint ‘/ws/apiprensa/getVideoUltimasSeccion’ contains an SQL injection vulnerability in the id_seccion parameter. The parameter is directly embedded in a complex SQL query that includes grouping and sorting operations. By injecting SQL syntax, an attacker can disrupt the query structure and cause database errors, exposing the internal logic of the queries. The complexity of the query increases the potential impact, as it could allow for broader manipulation of the content retrieval logic.
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker can manipulate a database query through a publicly reachable iSquad video-content endpoint. Successful abuse could expose or alter sensitive data, although the supplied CVSS assessment indicates no direct availability impact. Organizations using iSquad should urgently determine whether this endpoint is exposed and obtain confirmed remediation guidance from TOOOLS or INCIBE-CERT.
Executive priority
Assign immediate ownership to identify exposed iSquad systems and obtain authoritative vendor remediation details. Prioritize internet-facing deployments because the supplied score indicates unauthenticated, low-complexity network exploitation with potentially high data confidentiality and integrity consequences.
Technical view
CVE-2026-81675 is a CWE-89 SQL injection in the id_seccion parameter of /ws/apiprensa/getVideoUltimasSeccion. The parameter is directly embedded in a complex query containing grouping and sorting logic. The supplied CVSS 4.0 vector rates network-based, unauthenticated exploitation as low complexity, with high confidentiality and integrity impact and no stated availability impact.
Likely exposure
Risk is greatest where an iSquad deployment exposes the affected endpoint to untrusted networks. Authentication is not required according to the CVSS vector. The supplied affected-version data lists version "0" while also reporting a default unaffected status, so organizations should not infer their status from that ambiguous version record alone.
Exploitation context
The supplied sources describe database-error disclosure and potential manipulation of content-retrieval logic. The CVE is not listed as KEV in the bundle, and no cited evidence establishes active exploitation, public exploit availability, or observed attacks. Treat the technical impact as serious without representing exploitation as confirmed.
Researcher notes
The record supports SQL injection and a critical CVSS 4.0 score of 9.3. However, affected-version information is ambiguous: version "0" is listed alongside a default unaffected status. The bundle does not identify a fixed version, concrete patch procedure, exploitation evidence, or demonstrated data extraction. Validate these points with TOOOLS and the INCIBE-CERT notice.
Mitigation direction
Review the INCIBE-CERT advisory and obtain TOOOLS guidance for confirmed affected and fixed versions.
Apply the vendor-supported update or remediation after validating its applicability to the deployed iSquad release.
Restrict untrusted access to the affected endpoint until confirmed remediation is deployed.
Use input validation and parameterized database queries if responsible for maintaining affected application code.
Monitor application and database logs for unusual errors or malformed id_seccion requests.
Validation and detection
Inventory all iSquad deployments, versions, and externally reachable application routes.
Verify whether /ws/apiprensa/getVideoUltimasSeccion is reachable from untrusted networks.
Review logs for database errors and anomalous requests involving the id_seccion parameter.
Confirm the remediated implementation no longer embeds id_seccion directly into SQL.
Test the vendor remediation safely in non-production before rollout.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
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.