# CVE-2017-18596: Missing authorization in n/a

> Attackers can bypass access controls on internal functions in the Elementor WordPress plugin, potentially leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vqg9-c22m-rj53

## What is CVE-2017-18596?

CVE-2017-18596 is a high-severity missing authorization vulnerability in n/a, published on 10 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The elementor plugin before 1.8.0 for WordPress has incorrect access control for internal functions.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Elementor Elementor Page Builder.

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

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

## Is CVE-2017-18596 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13126](https://insights.sbomify.com/CVE-2020-13126/): File upload in n/a (critical 9.9)
- [CVE-2020-7055](https://insights.sbomify.com/CVE-2020-7055/): File upload in n/a (critical 9.9)
- [CVE-2025-3076](https://insights.sbomify.com/CVE-2025-3076/): Elementor Pro <= 3.29.0 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2018-18379](https://insights.sbomify.com/CVE-2018-18379/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-20406](https://insights.sbomify.com/CVE-2020-20406/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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