dbcve.org
I EducarApplication · Portabilis

CVE-2025-10846

HIGH · 8.8 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to after 2.10.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability was determined in Portabilis i-Educar up to 2.10. This vulnerability affects unknown code of the file /module/ComponenteCurricular/edit. This manipulation of the argument ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

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 · moderate confidence

SQL injection vulnerability in Portabilis i-Educar up to v2.10 allows remote attackers to inject malicious SQL queries via the ID parameter in the /module/ComponenteCurricular/edit endpoint. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement strict input validation on the ID parameter. Conduct a comprehensive code audit to identify and remediate additional SQL injection vulnerabilities throughout the application.

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
I EducarApplication
Affected:<= 2.10.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify i-Educar installation and version
    Locate the i-Educar installation directory or check the application footer/version page to find the installed version number. Compare it to the affected range: versions <= 2.10.0 are vulnerable.
    Affected if The installed version of Portabilis i-Educar is 2.10.0 or lower.
  2. Verify vulnerable endpoint exists
    Check if the web application responds to the /module/ComponenteCurricular/edit endpoint. This can be done by accessing the URL or reviewing server access logs for requests to this path.
    Affected if The endpoint /module/ComponenteCurricular/edit is present and accessible in the i-Educar installation.
  3. Confirm ID parameter acceptance
    If source code is available, examine the controller handling the /module/ComponenteCurricular/edit route and locate the code that processes the ID parameter. Look for direct usage of this parameter in database queries without proper sanitization or parameterized queries.
    Affected if The ID parameter from the edit endpoint is used directly in SQL queries without prepared statements or input validation.
  4. Review database query implementation
    Examine the database interaction code for the ComponenteCurricular module. Check whether SQL queries are constructed dynamically with string concatenation or whether they use parameterized queries/prepared statements.
    Affected if SQL queries in the ComponenteCurricular edit functionality use string concatenation or interpolation rather than bound parameters.

A defender is affected if running Portabilis i-Educar version 2.10.0 or earlier, the /module/ComponenteCurricular/edit endpoint exists, and the ID parameter is used directly in SQL queries without parameterized prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.10.0
Interim mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements and implement strict input validation on the ID parameter. Conduct a comprehensive code audit to identify and remediate additional SQL injection vulnerabilities throughout the application.

Fix this in I Educar Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10846 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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