# CVE-2019-25738: WordPress Hybrid Composer 1.4.6 Unauthenticated Settings Change

> Unauthenticated attackers can modify WordPress settings to enable registration and set default roles to administrator, leading to account takeover.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-p9g9-jpx8-w224

## What is CVE-2019-25738?

CVE-2019-25738 is a critical missing authorization vulnerability in framework-y Hybrid Composer, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Hybrid Composer 1.4.6 contains an unauthenticated settings change vulnerability that allows unauthenticated attackers to modify WordPress options by exploiting the hc_ajax_save_option action. Attackers can send POST requests to the admin-ajax.php endpoint with the action parameter set to hc_ajax_save_option to enable user registration and set the default role to administrator, enabling account takeover.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2019-25738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25738 is a critical missing authorization vulnerability in framework-y Hybrid Composer, published on 4 Jun 2026. 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-25738 exists.

Affected product: framework-y Hybrid Composer. 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-25738/ (Markdown: https://insights.sbomify.com/CVE-2019-25738/index.md)
```

## Sources

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

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