# CVE-2022-1418: Social Stickers <= 2.2.9 - Stored Cross-Site Scripting via CSRF

> Attackers can inject malicious scripts via CSRF in Social Stickers plugin settings, potentially executing code in admin sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5r8p-c5pv-rv87

## What is CVE-2022-1418?

CVE-2022-1418 is a medium-severity cross-site scripting vulnerability in Unknown Social Stickers, published on 16 May 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

The Social Stickers WordPress plugin through 2.2.9 does not have CSRF checks in place when updating its Social Network settings, and does not escape some of these fields, which could allow attackers to make a logged-in admin change them and lead to Stored Cross-Site Scripting issues.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Pluginmirror Social Stickers.

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

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

## Is CVE-2022-1418 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1418 is a medium-severity cross-site scripting vulnerability in Unknown Social Stickers, published on 16 May 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-1418 in the wild and no public exploit code.

Affected product: Unknown Social Stickers. 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-1418/ (Markdown: https://insights.sbomify.com/CVE-2022-1418/index.md)
```

## Sources

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

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