CVE-2025-9724
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 determined in Portabilis i-Educar up to 2.10. This impacts an unknown function of the file /intranet/educar_nivel_ensino_cad.php. Executing manipulation of the argument nm_nivel/descricao can lead to cross site scripting. The attack can be launched 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 confidenceCross-site scripting (XSS) vulnerability in Portabilis i-Educar education management system allows remote attackers to inject malicious scripts via the nm_nivel or descricao parameters in /intranet/educar_nivel_ensino_cad.php. The unsanitized user input is reflected back to the browser, enabling session hijacking or defacement attacks.
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.10CVSS 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.
-
Verify the affected PHP file exists in your deploymentLocate the file /intranet/educar_nivel_ensino_cad.php within your web server document root. Common paths include /var/www/html/intranet/ or similar web root directories.Affected if The file exists and is accessible via the web server, meaning the vulnerable component is present in your environment.
-
Determine your installed version of Portabilis i-EducarCheck your i-Educar installation for the version number. This is often found in a composer.json, package.json, or a version.php file within the application root. Compare your version against the affected range: versions 2.10 and below.Affected if Your installed version is 2.10 or lower, placing it within the vulnerable version range.
-
Confirm the vulnerable endpoint is accessibleAccess the URL endpoint /intranet/educar_nivel_ensino_cad.php via HTTP or HTTPS and verify the page loads. Attempt to access it with a test query parameter such as ?nm_nivel=test to see if your input is reflected back in the response.Affected if The endpoint loads and your test input is reflected in the HTML output without encoding or sanitization, confirming the XSS vulnerability is present.
-
Inspect the application response for lack of output encodingSubmit a harmless test payload such as <script>alert(1)</script> in the nm_nivel or descricao parameter, then view the page source of the response. Check whether the payload appears as literal text or as an actual script tag that could execute.Affected if The payload renders as executable HTML/JavaScript in the browser response, indicating the input is not being escaped and the vulnerability is exploitable.
You are affected if your i-Educar version is 2.10 or below and the /intranet/educar_nivel_ensino_cad.php endpoint reflects unsanitized nm_nivel or descricao parameters back to users.
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/escaping for all user-supplied parameters in the affected PHP file. Additionally, configure Content-Security-Policy headers to mitigate XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9724 — 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-9724 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