# CVE-2013-3958: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access to Siemens WinCC Web Navigator using hardcoded credentials, compromising industrial control systems.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5vff-97qq-6xwp

## What is CVE-2013-3958?

CVE-2013-3958 is a high-severity vulnerability in n/a, published on 14 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The login implementation in the Web Navigator in Siemens WinCC before 7.2 Update 1, as used in SIMATIC PCS7 8.0 SP1 and earlier and other products, has a hardcoded account, which makes it easier for remote attackers to obtain access via an unspecified request.

Weakness: CWE-255

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

It affects 2 products.


Products: Siemens Simatic Pcs7, Siemens Wincc.

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

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

## Is CVE-2013-3958 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8551](https://insights.sbomify.com/CVE-2014-8551/): Code injection in n/a (critical 10.0)
- [CVE-2013-3957](https://insights.sbomify.com/CVE-2013-3957/): SQL injection in n/a (high 7.5)
- [CVE-2012-3032](https://insights.sbomify.com/CVE-2012-3032/): SQL injection in n/a (high 7.5)
- [CVE-2012-3015](https://insights.sbomify.com/CVE-2012-3015/): Privilege escalation in n/a (medium 6.9)
- [CVE-2014-4686](https://insights.sbomify.com/CVE-2014-4686/): Hardcoded credentials in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3958 is a high-severity vulnerability in n/a, published on 14 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3958 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-3958/ (Markdown: https://insights.sbomify.com/CVE-2013-3958/index.md)
```

## Sources

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

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