# CVE-2022-27174: Cross-site request forgery in Easy Blog for EC-CUBE4

> A CSRF vulnerability in the Easy Blog plugin for EC-CUBE4 allows attackers to delete blog articles or categories by tricking administrators into visiting a malicious page.

- **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:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v77w-mgq7-vjj2

## What is CVE-2022-27174?

CVE-2022-27174 is a medium-severity vulnerability in COREMOBILE Co. Ltd. Easy Blog for EC-CUBE4, published on 13 Jun 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

Cross-site request forgery (CSRF) vulnerability in Easy Blog for EC-CUBE4 Ver.1.0.1 and earlier allows a remote unauthenticated attacker to hijack the authentication of the administrator and delete a blog article or a category via a specially crafted page.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Easy Blog Project Easy Blog.

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

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

## Is CVE-2022-27174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27174 is a medium-severity vulnerability in COREMOBILE Co. Ltd. Easy Blog for EC-CUBE4, published on 13 Jun 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-27174 in the wild and no public exploit code.

Affected product: COREMOBILE Co. Ltd. Easy Blog for EC-CUBE4. 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-27174/ (Markdown: https://insights.sbomify.com/CVE-2022-27174/index.md)
```

## Sources

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

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