CVE-2025-7868
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 found in Portabilis i-Educar up to 2.10. This issue affects some unknown processing of the file /intranet/educar_calendario_dia_motivo_cad.php of the component Calendar Module. The manipulation of the argument Motivo/descricao results in cross site scripting. It is possible to launch the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in Portabilis i-Educar up to version 2.10 within the Calendar Module (educar_calendario_dia_motivo_cad.php). The 'Motivo/descricao' parameter accepts unsanitized user input that is reflected back to other users, allowing execution of malicious JavaScript in the context of the victim's browser. The attack can be launched remotely and a public exploit exists.
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 if Portabilis i-Educar is deployedLocate the i-Educar web application in your environment by checking web server document roots or application directories for the presence of the i-Educar codebaseAffected if i-Educar is present in the environment
-
Determine the installed version of i-EducarCheck the application version file, composer.json, or administrative interface for the i-Educar version numberAffected if The version is 2.10.0 or lower
-
Verify the Calendar Module file existsLocate the file educar_calendario_dia_motivo_cad.php within the application directory structure, typically under the modules or src folderAffected if The vulnerable file exists in the installation
-
Check if the Calendar Module is accessibleAttempt to access the Calendar Module administrative interface or the specific endpoint for educator_calendario_dia_motivo_cad.php via HTTP requestAffected if The module is enabled and accessible to users
-
Test for unsanitized input reflectionSubmit a test payload (such as <script>alert('XSS')</script>) in the 'Motivo/descricao' parameter through the Calendar Module form, then retrieve or view the submitted data to observe if the payload is executed without encodingAffected if The submitted payload is reflected and executed in the browser without HTML entity encoding
A user is affected if Portabilis i-Educar version 2.10.0 or lower is installed, the Calendar Module is accessible, and the 'Motivo/descricao' parameter reflects user input without sanitization.
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 context-aware output encoding and input validation/sanitization for all user-supplied data in the Calendar Module. Apply proper HTML entity encoding before rendering user input. Consider deploying a web application firewall (WAF) as an interim control until the code-level fix is applied.
- 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-7868 — 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-7868 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