# CVE-2015-2792: Security feature bypass in n/a

> Remote attackers can bypass nonce checks in the WPML plugin to perform arbitrary actions by manipulating request parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 30 Mar 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-657c-v2h8-hpvj

## What is CVE-2015-2792?

CVE-2015-2792 is a high-severity vulnerability in n/a, published on 30 Mar 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WPML plugin before 3.1.9 for WordPress does not properly handle multiple actions in a request, which allows remote attackers to bypass nonce checks and perform arbitrary actions via a request containing an action POST parameter, an action GET parameter, and a valid nonce for the action GET parameter.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-2792?

It affects 1 product.


Products: Wpml Wpml.

## How do I fix CVE-2015-2792?

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

## Is CVE-2015-2792 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-6386](https://insights.sbomify.com/CVE-2024-6386/): Code injection in WPML (critical 9.9)
- [CVE-2015-2314](https://insights.sbomify.com/CVE-2015-2314/): SQL injection in n/a (high 7.5)
- [CVE-2025-3488](https://insights.sbomify.com/CVE-2025-3488/): Cross-site scripting in WPML (medium 6.4)
- [CVE-2015-2791](https://insights.sbomify.com/CVE-2015-2791/): Missing authorization in n/a (medium 6.4)
- [CVE-2018-18069](https://insights.sbomify.com/CVE-2018-18069/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2792 and fix it if it is affected.

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

## Sources

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

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