# CVE-2022-40842: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in the NdkAdvancedCustomizationFields plugin to access internal resources or bypass security controls.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 22 Nov 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-r3f7-hpwv-5qc2

## What is CVE-2022-40842?

CVE-2022-40842 is a critical server-side request forgery vulnerability in n/a, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ndk design NdkAdvancedCustomizationFields 3.5.0 is vulnerable to Server-side request forgery (SSRF) via rotateimg.php.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-40842?

It affects 1 product.


Products: Ndk-Design Ndkadvancedcustomizationfields.

## How do I fix CVE-2022-40842?

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

## Is CVE-2022-40842 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40839](https://insights.sbomify.com/CVE-2022-40839/): SQL injection in n/a (high 7.5)
- [CVE-2022-40841](https://insights.sbomify.com/CVE-2022-40841/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-40840](https://insights.sbomify.com/CVE-2022-40840/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40842 and fix it if it is affected.

What it is: CVE-2022-40842 is a critical server-side request forgery vulnerability in n/a, published on 22 Nov 2022. 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-2022-40842 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-2022-40842/ (Markdown: https://insights.sbomify.com/CVE-2022-40842/index.md)
```

## Sources

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

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