# CVE-2019-6703: Missing authorization in n/a

> Unauthenticated attackers can modify WordPress options to enable registration and set default roles to Administrator, leading to site takeover.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-47jw-726h-2367

## What is CVE-2019-6703?

CVE-2019-6703 is a critical missing authorization vulnerability in n/a, published on 27 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in migla_ajax_functions.php in the Calmar Webmedia Total Donations plugin through 2.0.5 for WordPress allows unauthenticated attackers to update arbitrary WordPress option values, leading to site takeover. These attackers can send requests to wp-admin/admin-ajax.php to call the miglaA_update_me action to change arbitrary options on affected sites. This can be used to enable new user registration and set the default role for new users to Administrator.

## Which versions are affected by CVE-2019-6703?

It affects 1 product.


Products: Calmar-Webmedia Total Donations.

## How do I fix CVE-2019-6703?

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

## Is CVE-2019-6703 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-6703 exists.

Public exploit code:

- Total Donations Plugin for WordPress < 2.0.6 - Arbitrary Options Update (nuclei): http/cves/2019/CVE-2019-6703.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6703 and fix it if it is affected.

What it is: CVE-2019-6703 is a critical missing authorization vulnerability in n/a, published on 27 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-6703 exists.

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-2019-6703/ (Markdown: https://insights.sbomify.com/CVE-2019-6703/index.md)
```

## Sources

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

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