# CVE-2021-38314: Gutenberg Template Library & Redux Framework <= 4.2.11 Sensitive Information Disclosure

> Unauthenticated attackers can predict AJAX actions to retrieve sensitive site configuration data, including plugin lists and hashed security keys.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2021
- **Updated:** 5 May 2025
- **Also known as:** GHSA-h223-3fmj-vhg5

## What is CVE-2021-38314?

CVE-2021-38314 is a medium-severity vulnerability in Redux.io Gutenberg Template Library & Redux Framework, published on 2 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Gutenberg Template Library & Redux Framework plugin <= 4.2.11 for WordPress registered several AJAX actions available to unauthenticated users in the `includes` function in `redux-core/class-redux-core.php` that were unique to a given site but deterministic and predictable given that they were based on an md5 hash of the site URL with a known salt value of '-redux' and an md5 hash of the previous hash with a known salt value of '-support'. These AJAX actions could be used to retrieve a list of active plugins and their versions, the site's PHP version, and an unsalted md5 hash of site’s `AUTH_KEY` concatenated with the `SECURE_AUTH_KEY`.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-760 (Use of a One-Way Hash with a Predictable Salt), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-38314?

It affects 1 product.


Products: Redux Gutenberg Template Library \& Redux Framework.

## How do I fix CVE-2021-38314?

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

## Is CVE-2021-38314 being exploited?

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

Public exploit code:

-  Unauthenticated Sensitive Information Disclosure (CVE-2021–38314). (github_poc): https://github.com/orangmuda/CVE-2021-38314
- https://github.com/phrantom/cve-2021-38314 (github_poc): https://github.com/phrantom/cve-2021-38314
- CVE-2021-38314 Python Exploit (github_poc): https://github.com/akhilkoradiya/CVE-2021-38314
- cve-2021-38314 - Unauthenticated Sensitive Information Disclosure (github_poc): https://github.com/twseptian/cve-2021-38314
- https://github.com/shubhayu-64/CVE-2021-38314 (github_poc): https://github.com/shubhayu-64/CVE-2021-38314
- Python exploit for CVE-2021-38314 (github_poc): https://github.com/c0ff33b34n/CVE-2021-38314

## Other vulnerabilities in Redux.io Gutenberg Template Library & Redux Framework

- [CVE-2021-38312](https://insights.sbomify.com/CVE-2021-38312/): Missing authorization in Gutenberg Template Library & Redux Framework (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38314 and fix it if it is affected.

What it is: CVE-2021-38314 is a medium-severity vulnerability in Redux.io Gutenberg Template Library & Redux Framework, published on 2 Sep 2021. 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-2021-38314 exists.

Affected product: Redux.io Gutenberg Template Library & Redux Framework. 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-2021-38314/ (Markdown: https://insights.sbomify.com/CVE-2021-38314/index.md)
```

## Sources

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

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