# CVE-2007-2595: Business logic in n/a

> Authenticated users can bypass account suspension by directly accessing the activation URL, restoring their account status to Active.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8gh7-9ww2-4ph8

## What is CVE-2007-2595?

CVE-2007-2595 is a medium-severity vulnerability in n/a, published on 11 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RSAuction 2.73.1.3 allows remote authenticated users to move their own account status from Suspended to Active via a direct request for the activation URL that is provided at the time of account registration. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2007-2595?

It affects 1 product.


Products: Rscript Rsauction.

## How do I fix CVE-2007-2595?

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

## Is CVE-2007-2595 being exploited?

There is no known exploitation of CVE-2007-2595 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2595 and fix it if it is affected.

What it is: CVE-2007-2595 is a medium-severity vulnerability in n/a, published on 11 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2595 in the wild and no public exploit code.

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-2007-2595/ (Markdown: https://insights.sbomify.com/CVE-2007-2595/index.md)
```

## Sources

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

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