# CVE-2010-5318: Auth bypass in n/a

> Remote attackers can reset the administrator password by specifying the admin email, leading to full account takeover.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 3 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xf63-wjjg-4c9f

## What is CVE-2010-5318?

CVE-2010-5318 is a medium-severity authentication bypass vulnerability in n/a, published on 3 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The password-reset feature in as/index.php in SweetRice CMS before 0.6.7.1 allows remote attackers to modify the administrator's password by specifying the administrator's e-mail address in the email parameter.

Weakness: CWE-255

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

It affects 1 product.


Products: Basic-Cms Sweetrice.

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

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

## Is CVE-2010-5318 being exploited?

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

Public exploit code:

- SweetRice 0.6.7 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-5317](https://insights.sbomify.com/CVE-2010-5317/): SQL injection in n/a (high 7.5)
- [CVE-2009-4231](https://insights.sbomify.com/CVE-2009-4231/): Path traversal in n/a (high 7.5)
- [CVE-2009-4224](https://insights.sbomify.com/CVE-2009-4224/): Code injection in n/a (medium 6.8)
- [CVE-2011-3804](https://insights.sbomify.com/CVE-2011-3804/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-5316](https://insights.sbomify.com/CVE-2010-5316/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5318 is a medium-severity authentication bypass vulnerability in n/a, published on 3 Jan 2015. 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-2010-5318 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-5318/ (Markdown: https://insights.sbomify.com/CVE-2010-5318/index.md)
```

## Sources

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

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