# CVE-2023-35858: Other in n/a

> Remote unauthenticated attackers can exploit XPath injection in blog and RSS functions to obtain application information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4v25-p375-pcjc

## What is CVE-2023-35858?

CVE-2023-35858 is a medium-severity vulnerability in n/a, published on 13 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XPath Injection vulnerabilities in the blog and RSS functions of Modern Campus - Omni CMS 2023.1 allow a remote, unauthenticated attacker to obtain application information.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2023-35858?

It affects 1 product.


Products: Moderncampus Omni Cms.

## How do I fix CVE-2023-35858?

No fix has been published for CVE-2023-35858 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-35858 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35858 exists.

## Other vulnerabilities in n/a

- [CVE-2022-40766](https://insights.sbomify.com/CVE-2022-40766/): SQL injection in n/a (critical 9.8)
- [CVE-2023-35859](https://insights.sbomify.com/CVE-2023-35859/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-35860](https://insights.sbomify.com/CVE-2023-35860/): Path traversal in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35858 and fix it if it is affected.

What it is: CVE-2023-35858 is a medium-severity vulnerability in n/a, published on 13 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35858 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-35858/ (Markdown: https://insights.sbomify.com/CVE-2023-35858/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35858
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35858
- OSV: https://osv.dev/vulnerability/CVE-2023-35858

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-35858/
Summaries are generated and may contain mistakes; the official description above is the record.