# CVE-2021-4227: Ark Comment Editor <= 2.15.6 - Iframe Injection via Comment

> Attackers can inject iframes into comments via the source editor, loading arbitrary content and potentially executing scripts in the victim's browser.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-h3w7-w9rh-w829

## What is CVE-2021-4227?

CVE-2021-4227 is a medium-severity cross-site scripting vulnerability in Unknown ark-commenteditor, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ark-commenteditor WordPress plugin through 2.15.6 does not properly sanitise or encode the comments when in Source editor, allowing attackers to inject an iFrame in the page and thus load arbitrary content from any page to the comment section

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Obg Ark Wysiwyg Comment Editor.

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

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

## Is CVE-2021-4227 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-4227 is a medium-severity cross-site scripting vulnerability in Unknown ark-commenteditor, published on 16 Jan 2024. 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-4227 exists.

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

## Sources

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

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