# CVE-2021-24226: AccessAlly < 3.5.7 - $_SERVER Superglobal Leakage

> The AccessAlly WordPress plugin leaks environment variables via serialized $_SERVER data on public order form pages, exposing sensitive configuration details.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 12 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3hqr-g258-rfxm

## What is CVE-2021-24226?

CVE-2021-24226 is a high-severity vulnerability in Unknown AccessAlly, published on 12 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the AccessAlly WordPress plugin before 3.5.7, the file "resource/frontend/product/product-shortcode.php" responsible for the [accessally_order_form] shortcode is dumping serialize($_SERVER), which contains all environment variables. The leakage occurs on all public facing pages containing the [accessally_order_form] shortcode, no login or administrator role is required.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Accessally Accessally.

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

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

## Is CVE-2021-24226 being exploited?

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

Public exploit code:

- AccessAlly <3.5.7 - Sensitive Information Leakage (nuclei): http/cves/2021/CVE-2021-24226.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24226 is a high-severity vulnerability in Unknown AccessAlly, published on 12 Apr 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-24226 exists.

Affected product: Unknown AccessAlly. 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-24226/ (Markdown: https://insights.sbomify.com/CVE-2021-24226/index.md)
```

## Sources

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

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