# CVE-2010-3603: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions via CSRF to rename files, causing denial of service and potential information exposure.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-579f-rm77-fpx9

## What is CVE-2010-3603?

CVE-2010-3603 is a medium-severity vulnerability in n/a, published on 24 Sep 2010. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the file manager service (Services/FileService.ashx) in mojoPortal 2.3.4.3 and 2.3.5.1 allows remote attackers to hijack the authentication of administrators for requests that rename arbitrary files, as demonstrated by causing the user.config file to be moved, leading to a denial of service (service stop) and possibly the exposure of sensitive information.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2010-3603?

It affects 1 product.


Products: Sourcetreesolutions Mojoportal.

## How do I fix CVE-2010-3603?

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

## Is CVE-2010-3603 being exploited?

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

Public exploit code:

- mojoportal - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5320](https://insights.sbomify.com/CVE-2013-5320/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2010-3602](https://insights.sbomify.com/CVE-2010-3602/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3603 and fix it if it is affected.

What it is: CVE-2010-3603 is a medium-severity vulnerability in n/a, published on 24 Sep 2010. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3603 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-2010-3603/ (Markdown: https://insights.sbomify.com/CVE-2010-3603/index.md)
```

## Sources

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

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