dbcve.org
I EducarApplication · Portabilis

CVE-2025-10591

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-17
Fix available
A fix is available. Upgrade to after 2.10.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 weakness has been identified in Portabilis i-Educar up to 2.10. This affects an unknown function of the file /intranet/educar_funcao_cad.php of the component Editar Função Page. This manipulation of the argument abreviatura/tipoacao causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

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

Portabilis i-Educar up to version 2.10 contains a stored cross-site scripting (XSS) vulnerability in the /intranet/educar_funcao_cad.php file. The 'abreviatura' and 'tipoacao' parameters are not properly sanitized before being rendered in the Editar Função page, allowing an attacker to inject malicious JavaScript code that executes in the context of other users' browsers.

MitigationImplement proper input validation and output encoding for the 'abreviatura' and 'tipoacao' parameters. Use context-appropriate encoding when displaying these values in HTML and consider adding Content-Security-Policy headers to further mitigate XSS risks.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Check i-Educar installed version
    Locate the version file or check the application header/footer for the version number. Common locations include a config file, composer.json, or the application login page.
    Affected if The installed version is 2.10.0 or lower
  2. Verify vulnerable file exists
    Check if /intranet/educar_funcao_cad.php exists in the web root directory of the i-Educar installation.
    Affected if The file exists and the application version is 2.10.0 or lower
  3. Check 'abreviatura' parameter handling
    Review the source code of educar_funcao_cad.php to see if the 'abreviatura' parameter is validated or sanitized before being stored and displayed. Look for htmlspecialchars, strip_tags, or other encoding functions.
    Affected if No input sanitization or output encoding is found for the 'abreviatura' parameter
  4. Check 'tipoacao' parameter handling
    Review the source code of educar_funcao_cad.php to see if the 'tipoacao' parameter is validated or sanitized before being stored and displayed.
    Affected if No input sanitization or output encoding is found for the 'tipoacao' parameter
  5. Verify stored XSS execution point
    Access the Editar Função page in the application and check if user-supplied 'abreviatura' or 'tipoacao' values are rendered without encoding when the page is redisplayed.
    Affected if User input is reflected in the HTML output without proper encoding

You are affected if running i-Educar version 2.10.0 or lower and the vulnerable parameters 'abreviatura' and 'tipoacao' in educar_funcao_cad.php lack proper sanitization or output encoding.

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 proper input validation and output encoding for the 'abreviatura' and 'tipoacao' parameters. Use context-appropriate encoding when displaying these values in HTML and consider adding Content-Security-Policy headers to further mitigate XSS risks.

Fix this in I Educar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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