dbcve.org
OpensisApplication · Os4ed

CVE-2023-38881

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 reflected cross-site scripting (XSS) vulnerability in the Community Edition version 9.0 of OS4ED's openSIS Classic allows remote attackers to execute arbitrary JavaScript in the web browser of a user, by including a malicious payload into any of the 'calendar_id', 'school_date', 'month' or 'year' parameters in 'CalendarModal.php'.

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 cross-site scripting (XSS) vulnerability in openSIS Classic Community Edition version 9.0 allows remote attackers to inject arbitrary JavaScript through the 'calendar_id', 'school_date', 'month', or 'year' parameters in CalendarModal.php. The vulnerability is reflected, meaning the malicious payload is returned directly in the response without proper sanitization, enabling session hijacking or defacement when users click crafted links.

MitigationImplement proper input validation and output encoding for all four affected parameters in CalendarModal.php, using context-appropriate escaping functions to neutralize script injection attempts.

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
OpensisApplication
Affected:= 9.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if openSIS is installed
    Search the web root directory for openSIS installation files or check for the presence of the 'opensis' directory structure. Common paths include /var/www/html/opensis or C:\inetpub\wwwroot\opensis.
    Affected if The openSIS application is found on the system.
  2. Verify the installed openSIS version
    Check the version file or header in the openSIS installation. Typically found in an about.php, version file, or the main index.php. Compare the version number to 9.0.
    Affected if The installed version is exactly 9.0 (version 9.0).
  3. Locate CalendarModal.php
    Search for CalendarModal.php in the web application directory structure. Common paths include /var/www/html/opensis/CalendarModal.php or within modules/directories.
    Affected if CalendarModal.php exists in the openSIS installation.
  4. Confirm web accessibility of the vulnerable script
    Attempt to access CalendarModal.php via HTTP/HTTPS request (e.g., curl or browser) to verify it is reachable through the web server.
    Affected if CalendarModal.php responds to web requests and is publicly or internally accessible.
  5. Check for affected parameter usage
    Examine the CalendarModal.php source code to identify if it processes the 'calendar_id', 'school_date', 'month', or 'year' GET/POST parameters without proper sanitization. Look for direct echo or print statements using these parameters.
    Affected if The code uses any of the four affected parameters (calendar_id, school_date, month, year) without input validation or output encoding.

A system is affected if it runs openSIS version 9.0 with the CalendarModal.php file accessible and the vulnerable parameters in use without sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all four affected parameters in CalendarModal.php, using context-appropriate escaping functions to neutralize script injection attempts.

Fix this in Opensis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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