CVE-2025-10584
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 vulnerability was identified in Portabilis i-Educar up to 2.10. Impacted is an unknown function of the file /intranet/educar_calendario_anotacao_cad.php. Such manipulation of the argument nm_anotacao/descricao leads to cross site scripting. It is possible to launch the attack remotely. The exploit is publicly available and might 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 · moderate confidenceCross-site scripting (XSS) vulnerability in Portabilis i-Educar up to version 2.10. The nm_anotacao and descricao parameters in /intranet/educar_calendario_anotacao_cad.php are not properly sanitized, allowing attackers to inject malicious JavaScript code through these fields.
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.10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify i-Educar installation and versionLocate the i-Educar installation directory and check for a version file or database version record. Look for files like version.php, or check the database schema version table if accessible.Affected if Installed version is 2.10.0 or lower (the specific vulnerable version range is <= 2.10.0)
-
Verify vulnerable endpoint existsCheck if the file /intranet/educar_calendario_anotacao_cad.php exists in the web root or application directory of the i-Educar installation.Affected if The file exists and the application is running version 2.10.0 or below
-
Confirm intranet module is accessibleVerify the /intranet/ path is accessible via the web server. Attempt to access the directory or check web server configuration for route allowances.Affected if The intranet module is exposed and reachable without additional authentication barriers
-
Check parameter handling in the vulnerable fileReview the source code of educar_calendario_anotacao_cad.php and inspect how nm_anotacao and descricao parameters are processed and output. Look for absence of htmlspecialchars, htmlentities, or other output encoding functions.Affected if The parameters are not sanitized with proper output encoding before being rendered in HTML responses
-
Test for reflected XSS existenceIf authorized and in a testing environment, submit a benign XSS payload (such as <script>alert(1)</script>) in the nm_anotacao or descricao parameters via the vulnerable endpoint and verify if the script executes upon page reload.Affected if The payload is reflected verbatim without encoding, indicating the XSS vulnerability is present and exploitable
The environment is affected if i-Educar version 2.10.0 or lower is installed, the vulnerable endpoint /intranet/educar_calendario_anotacao_cad.php exists, and the nm_anotacao/descricao parameters lack proper output encoding.
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 proper input validation and output encoding for the nm_anotacao and descricao parameters. Additionally, apply context-appropriate output encoding when rendering these values in the browser to prevent script execution.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10584 — 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-10584 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