# CVE-2012-4280: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to add or modify agents via CSRF in Free Realty.

- **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:** 13 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x33f-ghcj-vx83

## What is CVE-2012-4280?

CVE-2012-4280 is a medium-severity vulnerability in n/a, published on 13 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in admin/agenteditor.php in Free Realty 3.1-0.6 allow remote attackers to hijack the authentication of administrators for requests that (1) add an agent via an addagent action or (2) modify an agent.

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

## Which versions are affected by CVE-2012-4280?

It affects 1 product.


Products: Rwcinc Free Realty.

## How do I fix CVE-2012-4280?

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

## Is CVE-2012-4280 being exploited?

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

Public exploit code:

- Free Realty 3.1-0.6 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4279](https://insights.sbomify.com/CVE-2012-4279/): SQL injection in n/a (high 7.5)
- [CVE-2012-4278](https://insights.sbomify.com/CVE-2012-4278/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4280 and fix it if it is affected.

What it is: CVE-2012-4280 is a medium-severity vulnerability in n/a, published on 13 Aug 2012. 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-2012-4280 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-2012-4280/ (Markdown: https://insights.sbomify.com/CVE-2012-4280/index.md)
```

## Sources

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

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