# CVE-2013-1245: Missing authorization in n/a

> Authenticated users can bypass access restrictions on user management fields due to client-side validation, potentially escalating privileges.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **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:** 16 May 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8crf-9q8h-hf3h

## What is CVE-2013-1245?

CVE-2013-1245 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The user-management page in Cisco WebEx Social relies on client-side validation of values in the Screen Name, First Name, Middle Name, Last Name, Email Address, and Job Title fields, which allows remote authenticated users to bypass intended access restrictions via crafted requests, aka Bug ID CSCue67190.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-1245?

It affects 1 product.


Products: Cisco Webex Social.

## How do I fix CVE-2013-1245?

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

## Is CVE-2013-1245 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3392](https://insights.sbomify.com/CVE-2013-3392/): Cross-site request forgery in n/a (medium 4.3)
- [CVE-2013-1107](https://insights.sbomify.com/CVE-2013-1107/): Information disclosure in n/a (medium 4.0)
- [CVE-2013-1244](https://insights.sbomify.com/CVE-2013-1244/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1245 and fix it if it is affected.

What it is: CVE-2013-1245 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1245 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-2013-1245/ (Markdown: https://insights.sbomify.com/CVE-2013-1245/index.md)
```

## Sources

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

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