CVE
openSIS local file inclusion in ajax.php modname
openSIS versions from 5.1 up to 9.0 are affected through the ajax.php modname parameter, with an authenticated user needed. CVSS rates it 8.7 (high). The product range ends at 9.0, but no fixed version is recorded.
- Exploited
- No known exploitation
- Fix
- Fixed in 9.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. openSIS version 5.1
Summary
openSIS 5.1 before 9.0 contains a local file inclusion vulnerability that allows authenticated users to include arbitrary files through the modname parameter of ajax.php. Attackers can prefix a payload with misc/ and use ../ directory traversal to read sensitive files like /etc/passwd or execute local scripts in the web server context. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.
Who should check
Teams running OS4ED openSIS 5.1 student information system
“openSIS 5.1 is vulnerable to local file inclusion”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
openSIS version 5.1Upgrade to a fixed version: 9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2012-20008 (openSIS 5.1 < 9.0 Authenticated Local File Inclusion via ajax.php modname), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2012-20008 (entry last updated 2026-11-18):
Affected:
- OS4ED openSIS: from 5.1, fixed in 9.0
Fixed versions: 9.0.
Conditions (all must be true for the bug to be hit):
- openSIS version 5.1 (source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensis-lfi.yaml)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2012-20008 is not listed as of cve.now's last read.
This KEV status is for CVE-2012-20008 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OS4ED/openSIS-Classic/commit/a2d617977fa159185263845ac75b8c83cddd07f0
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensis-lfi.yaml
- https://www.vulncheck.com/advisories/opensis-5.1-authenticated-local-file-inclusion-via-ajax-php-modname
- https://www.vulncheck.com/advisories/opensis-5.1-9.0-authenticated-local-file-inclusion-via-ajax-php-modname
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2012-20008
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2012-20008"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OS4ED openSIS
From 5.1 · fixed in 9.0
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2012-20008 |
| Record | NVD · CVE-2012-20008 |
| Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | Exploit-DB · Exploit EDB-38039 |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/other/opensis-lfi.yaml |
| Other links 3 | |
| Patch | GitHub · OS4ED/openSIS-Classic · Commit a2d61797 |
| Link | vulncheck.com · advisories/opensis-5.1-authenticated-local-file-inclusion-via-ajax-php-modname |
| Link | vulncheck.com · advisories/opensis-5.1-9.0-authenticated-local-file-inclusion-via-ajax-php-modname |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2012-20008
Is CVE-2012-20008 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can use the ajax.php modname parameter to include arbitrary local files. This can expose sensitive information and run local scripts in the context of the web server process, which may lead to compromise of the application and the computer.Source: github.com
Which versions are affected by CVE-2012-20008?
openSIS: from 5.1 before 9.0.Source: cve.now feed data
Am I affected, and how do I check?
The affected product range is openSIS 5.1 up to, but not including, 9.0. To check an installation, look at the openSIS version in the application.Source: github.com
How do I fix CVE-2012-20008?
No fixed version or vendor patch is recorded in the advisory data, so the upgrade target is not confirmed. The product range ends at 9.0, so confirm the fix with OS4ED before relying on 9.0.Source: github.com