# CVE-2013-6969: Other in n/a

> Remote attackers can modify unspecified fields on the Cisco WebEx Training Center registration page, potentially compromising data integrity.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 14 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2fp2-wfm4-76mp

## What is CVE-2013-6969?

CVE-2013-6969 is a medium-severity vulnerability in n/a, published on 14 Dec 2013. It can be exploited over the network.

### Official description

The training-registration page in Cisco WebEx Training Center allows remote attackers to modify unspecified fields via unknown vectors, aka Bug ID CSCul35990.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Webex Training Center.

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

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

## Is CVE-2013-6969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6710](https://insights.sbomify.com/CVE-2013-6710/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-1109](https://insights.sbomify.com/CVE-2013-1109/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-6966](https://insights.sbomify.com/CVE-2013-6966/): Open redirect in n/a (medium 5.8)
- [CVE-2013-6971](https://insights.sbomify.com/CVE-2013-6971/): Open redirect in n/a (medium 5.8)
- [CVE-2013-6709](https://insights.sbomify.com/CVE-2013-6709/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6969 is a medium-severity vulnerability in n/a, published on 14 Dec 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-6969 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-6969/ (Markdown: https://insights.sbomify.com/CVE-2013-6969/index.md)
```

## Sources

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

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