dbcve.org
I EducarApplication · Portabilis

CVE-2023-5578

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-14
Fix available
A fix is available. Upgrade to after 2.7.5 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 vulnerability was found in Portábilis i-Educar up to 2.7.5. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file \intranet\agenda_imprimir.php of the component HTTP GET Request Handler. The manipulation of the argument cod_agenda with the input ");'> <script>alert(document.cookie)</script> leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-242143. NOTE: 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 confidence

A reflected XSS vulnerability exists in Portábilis i-Educar up to 2.7.5 in the file intranet/agenda_imprimir.php. The cod_agenda GET parameter is not properly sanitized before being rendered in the HTML output, allowing injection of malicious script tags via the payload ");'> <script>alert(document.cookie)</script>. This can be exploited remotely to steal session cookies or perform actions in the context of authenticated users.

MitigationImplement proper input validation and output encoding for the cod_agenda parameter. Use context-appropriate escaping (HTML entity encoding) when rendering user-supplied data in HTML pages, or employ a whitelist-based validation approach for the parameter.

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.7.5

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. Confirm the product is Portabilis i-Educar
    Identify the installed application name and version through your software inventory, system documentation, or by accessing the application's admin panel or about page
    Affected if The product is not Portabilis i-Educar (this CVE only applies to this specific product)
  2. Check if your i-Educar version is affected
    Compare your installed version against the vulnerable range: any version <= 2.7.5. Check your application version through the admin interface, version file, or package management system
    Affected if Your installed version is 2.7.5 or any earlier version
  3. Locate the vulnerable script file
    Check if the file intranet/agenda_imprimir.php exists in your web server document root. Navigate to the intranet directory and verify the presence of agenda_imprimir.php
    Affected if The file intranet/agenda_imprimir.php exists and is accessible via the web server
  4. Inspect the cod_agenda parameter handling
    Open intranet/agenda_imprimir.php in a text editor and locate the code that handles the cod_agenda GET parameter. Search for lines that retrieve this parameter using $_GET['cod_agenda'] or similar
    Affected if The file retrieves and uses the cod_agenda parameter from the URL without sanitization
  5. Verify lack of output encoding
    Examine the code around where cod_agenda is used. Look for absence of htmlspecialchars(), htmlentities(), or similar output encoding functions when the parameter value is echoed or printed into the HTML response
    Affected if The cod_agenda value is directly output into HTML without encoding or escaping functions

You are affected if you are running Portabilis i-Educar version 2.7.5 or earlier and the file intranet/agenda_imprimir.php exists with the cod_agenda parameter being rendered in HTML without 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.7.5
Interim mitigation

Implement proper input validation and output encoding for the cod_agenda parameter. Use context-appropriate escaping (HTML entity encoding) when rendering user-supplied data in HTML pages, or employ a whitelist-based validation approach for the parameter.

Fix this in I Educar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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