CVE-2025-41373
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA SQL injection vulnerability has been found in Gandia Integra Total of TESI from version 2.1.2217.3 to v4.4.2236.1. The vulnerability allows an authenticated attacker to retrieve, create, update and delete databases through the 'idestudio' parameter in /encuestas/integraweb[_v4]/integra/html/view/hislistadoacciones.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the 'idestudio' parameter of hislistadoacciones.php in Gandia Integra Total allows authenticated attackers to execute arbitrary SQL queries, enabling full database compromise including retrieval, creation, update, and deletion of database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.1.2217.3, <= 4.4.2236.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Gandia Integra Total is installedLocate the web application installation directory or check for 'hislistadoacciones.php' file on the web server. Common paths may include the web root or application-specific directories.Affected if The file hislistadoacciones.php exists in the application directory structure.
-
Determine the installed versionCheck the application's version information, typically found in an about page, configuration file, or software metadata. Compare your version against the affected range: 2.1.2217.3 through 4.4.2236.1.Affected if The installed version falls within >= 2.1.2217.3 and <= 4.4.2236.1.
-
Verify the vulnerable parameter existsLocate hislistadoacciones.php and examine the code for the 'idestudio' parameter handling. Look for direct use of this parameter in SQL queries without parameterized queries.Affected if The file contains SQL queries using the 'idestudio' parameter without prepared statements or input sanitization.
-
Check if the application requires authenticationReview the application's authentication mechanism for hislistadoacciones.php. Determine if unauthenticated access is possible or if attacker needs valid credentials.Affected if An attacker can obtain valid authentication credentials to access the vulnerable endpoint.
-
Assess network exposureDetermine if the web application is accessible over the network. Check firewall rules, network ACLs, or if the application is exposed to the internet or untrusted networks.Affected if The application is accessible from network segments where untrusted users can reach it and attempt exploitation.
You are affected if Gandia Integra Total version 2.1.2217.3 through 4.4.2236.1 is installed, the vulnerable hislistadoacciones.php file exists with the unpatched 'idestudio' parameter, and an authenticated user can access the endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries (prepared statements) for all database operations involving the 'idestudio' parameter. Apply vendor-provided patch when available. If immediate patching is not possible, deploy a WAF rule to filter malicious SQL injection payloads in this parameter.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41373 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41373 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data