CVE-2023-35860
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 Directory Traversal vulnerability in Modern Campus - Omni CMS 2023.1 allows a remote, unauthenticated attacker to enumerate file system information via the dir parameter to listing.php or rss.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 confidenceDirectory traversal vulnerability in Modern Campus Omni CMS 2023.1 allows unauthenticated remote attackers to access file system information via the dir parameter in listing.php or rss.php by manipulating path traversal sequences.
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= 2023.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Modern Campus Omni CMS installationLocate the web application root directory and confirm the presence of Modern Campus Omni CMS files, or check the application's main page for the product name and version disclosure.Affected if The product is not Modern Campus Omni CMS - not affected.
-
Verify the installed version is 2023.1Check the application's version information through the admin panel, version file, or HTTP headers/responses. Compare your installed version to the affected range (= 2023.1).Affected if Version is exactly 2023.1 - potentially affected. Versions other than 2023.1 are not in the affected range.
-
Confirm listing.php endpoint existsCheck for the file 'listing.php' in the web root or common CMS directories by attempting to access it via HTTP (e.g., GET /listing.php).Affected if File does not exist - not affected.
-
Confirm rss.php endpoint existsCheck for the file 'rss.php' in the web root or common CMS directories by attempting to access it via HTTP (e.g., GET /rss.php).Affected if File does not exist - not affected.
-
Test dir parameter availabilitySend a request to listing.php or rss.php with a benign parameter such as '?dir=test' and observe if the application processes it without proper validation.Affected if The dir parameter is accepted and processed - vulnerable to path traversal if no validation exists.
You are affected if Modern Campus Omni CMS version 2023.1 is installed AND the listing.php or rss.php endpoints exist and accept the dir parameter 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 strict input validation and path sanitization on the dir parameter to prevent traversal sequences; restrict file system access and validate all paths against an allowed whitelist.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35860 — 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-2023-35860 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