# CVE-2022-4397: morontt zend-blog-number-2 Comment Comment.php cross-site request forgery

> Attackers can perform unauthorized actions on behalf of authenticated users in the Zend Blog Number 2 plugin via cross-site request forgery.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-87pw-2ggr-vr38

## What is CVE-2022-4397?

CVE-2022-4397 is a medium-severity vulnerability in morontt zend-blog-number-2, published on 10 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in morontt zend-blog-number-2. It has been classified as problematic. Affected is an unknown function of the file application/forms/Comment.php of the component Comment Handler. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The name of the patch is 36b2d4abe20a6245e4f8df7a4b14e130b24d429d. It is recommended to apply a patch to fix this issue. VDB-215250 is the identifier assigned to this vulnerability.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Zend-Blog-2 Project Zend-Blog-2.

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

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

## Is CVE-2022-4397 being exploited?

There is no known exploitation of CVE-2022-4397 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4397 is a medium-severity vulnerability in morontt zend-blog-number-2, published on 10 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4397 in the wild and no public exploit code.

Affected product: morontt zend-blog-number-2. 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-4397/ (Markdown: https://insights.sbomify.com/CVE-2022-4397/index.md)
```

## Sources

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

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