CVE-2023-35859
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 Reflected Cross-Site Scripting (XSS) vulnerability in the blog function of Modern Campus - Omni CMS 2023.1 allows a remote attacker to inject arbitrary scripts or HTML via multiple parameters.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in the blog function of Modern Campus Omni CMS 2023.1 allows remote attackers to inject arbitrary JavaScript or HTML via multiple parameters in the blog functionality. The attack is reflected back to the user without proper input sanitization or output encoding.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Omni CMS versionCheck your Modern Campus Omni CMS installation for the exact version number. This is typically found in the admin panel under System Information, About, or in the footer of admin pages. Compare it to the affected version: 2023.1Affected if The installed version is exactly 2023.1
-
Confirm blog module is accessibleNavigate to or verify access to the blog functionality within Omni CMS. This is typically found under Content, Modules, or a specific Blogs section in the CMS navigation. Check if the blog feature is enabled in your installation.Affected if The blog function is enabled and accessible to users or attackers
-
Identify blog-related URLsLocate URLs that access the blog functionality. Look for paths containing 'blog' in your Omni CMS web interface, such as /blog, /blogs, or similar endpoints. These are the potential entry points for the reflected XSS.Affected if Blog-related URLs are accessible without authentication or to authenticated users
-
Test for reflected parametersReview the blog function's request parameters (GET or POST) by interacting with the blog pages. Identify any user-controllable parameters that are reflected back in the response without sanitization. Common parameters include id, page, category, search, or similar query parameters.Affected if Parameters in blog URLs are reflected in the page response without proper encoding
You are affected if you are running Modern Campus Omni CMS version 2023.1 and the blog function is enabled and accessible, as the reflected XSS can be triggered through blog parameters.
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 dataApply vendor-provided patch for Omni CMS 2023.1. Implement input validation and output encoding for all user-supplied parameters in the blog function as a defense-in-depth measure.
- 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-2023-35859 — 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-35859 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