I EducarApplication · Portabilis

CVE-2025-10845

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 found in Portabilis i-Educar up to 2.10. This affects an unknown part of the file /module/ComponenteCurricular/view. The manipulation of the argument ID results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.

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 confidence

SQL injection vulnerability in Portabilis i-Educar's ComponenteCurricular module view file, where the ID parameter is not properly sanitized before being used in SQL queries. This allows remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries or prepared statements for all database operations using the ID parameter. Apply input validation and escaping. Consider updating to version 2.10.1 or later if a patched release is available.

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. Confirm Portabilis i-Educar is installed
    Identify the presence of the i-Educar application in your environment. This is a Brazilian educational management system. Check your web server logs, installed applications, or consult your system administrator.
    Affected if The application is present in the environment
  2. Check installed version
    Locate the version information for your i-Educar installation. Common locations include: configuration files (config.php, .env), a footer or about page in the web interface, or the composer.json file if using PHP package manager. Compare your version against the affected range of <= 2.10.0
    Affected if The installed version is 2.10.0 or any earlier version
  3. Verify ComponenteCurricular module is accessible
    Check if the ComponenteCurricular (Curricular Component) module is enabled and accessible in your i-Educar installation. This module typically manages curriculum/course subject data. Attempt to access the module URL path such as /module/ComponenteCurricular or similar paths containing 'componente' in the URL.
    Affected if The module is enabled and publicly or internally accessible
  4. Test for SQL injection via ID parameter
    If the module is accessible, test the ID parameter for SQL injection by submitting a request with a single quote (') or boolean-based payloads (e.g., ID=1' OR '1'='1) to the ComponenteCurricular view endpoint. Monitor for SQL error messages in the response or unexpected data leakage.
    Affected if The application returns SQL syntax errors or behaves unexpectedly when special characters are submitted in the ID parameter, indicating unsanitized input is used in database queries

You are affected if Portabilis i-Educar version 2.10.0 or earlier is installed and the ComponenteCurricular module is accessible with the ID parameter vulnerable to SQL injection.

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

Implement parameterized queries or prepared statements for all database operations using the ID parameter. Apply input validation and escaping. Consider updating to version 2.10.1 or later if a patched release is available.

Fix this in I Educar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10845 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10845 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