# CVE-2017-3506: Oracle WebLogic Server OS Command Injection

> Unauthenticated attackers can compromise Oracle WebLogic Server via HTTP to read, create, delete, or modify critical data.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 3 Jun 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-2f3c-chf6-54v5

## What is CVE-2017-3506?

CVE-2017-3506 is a high-severity command injection vulnerability in Oracle Weblogic Server, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.0, 12.2.1.1 and 12.2.1.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data as well as unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2017-3506?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2017-3506?

No fix has been published for CVE-2017-3506 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Jun 2024.

## Is CVE-2017-3506 being exploited?

Yes. Attackers have exploited CVE-2017-3506 in the wild since at least 3 Jun 2024.

Public exploit code:

- CVE-2017-3506 (github_poc): https://github.com/Al1ex/CVE-2017-3506
- CVE-2017-3506 (github_poc): https://github.com/ianxtianxt/CVE-2017-3506
- Oracle Fusion Middleware Weblogic Server - Remote OS Command Execution (nuclei): http/cves/2017/CVE-2017-3506.yaml

## Other vulnerabilities in Oracle Weblogic Server

- [CVE-2020-14750](https://insights.sbomify.com/CVE-2020-14750/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14882](https://insights.sbomify.com/CVE-2020-14882/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14644](https://insights.sbomify.com/CVE-2020-14644/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-2883](https://insights.sbomify.com/CVE-2020-2883/): Oracle WebLogic Server Unspecified (critical 9.8, exploited in the wild)
- [CVE-2020-2551](https://insights.sbomify.com/CVE-2020-2551/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3506 and fix it if it is affected.

What it is: CVE-2017-3506 is a high-severity command injection vulnerability in Oracle Weblogic Server, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-3506 in the wild since at least 3 Jun 2024.

Affected product: Oracle Weblogic Server. 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-2017-3506/ (Markdown: https://insights.sbomify.com/CVE-2017-3506/index.md)
```

## Sources

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

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