# CVE-2025-0421: iFrame Injection in Mikrogrup's Shopside

> Attackers can inject iframes to overlay UI elements, potentially deceiving users or bypassing security controls in the Shopside platform.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-hfj2-6g68-rgrj

## What is CVE-2025-0421?

CVE-2025-0421 is a medium-severity cross-site scripting vulnerability in Shopside, published on 19 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Restriction of Rendered UI Layers or Frames vulnerability in Shopside Software Technologies Inc. Shopside allows iFrame Overlay.

This issue affects Shopside: through 05022025.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2025-0421?


## How do I fix CVE-2025-0421?

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

## Is CVE-2025-0421 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0421 and fix it if it is affected.

What it is: CVE-2025-0421 is a medium-severity cross-site scripting vulnerability in Shopside, published on 19 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0421 in the wild and no public exploit code.

Affected product: Shopside. 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-2025-0421/ (Markdown: https://insights.sbomify.com/CVE-2025-0421/index.md)
```

## Sources

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

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