# CVE-2024-12271: 360 Javascript Viewer <= 1.7.29 - Authenticated (Administrator+) Stored Cross-Site Scripting

> Administrators can inject scripts via the ref parameter in multi-site or unfiltered_html-disabled WordPress installations, leading to script execution.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7r69-4p34-c2pw

## What is CVE-2024-12271?

CVE-2024-12271 is a medium-severity cross-site scripting vulnerability in jtermaat 360 Javascript Viewer, published on 12 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The 360 Javascript Viewer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ref’ parameter in all versions up to, and including, 1.7.29 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-12271?


## How do I fix CVE-2024-12271?

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

## Is CVE-2024-12271 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12271 and fix it if it is affected.

What it is: CVE-2024-12271 is a medium-severity cross-site scripting vulnerability in jtermaat 360 Javascript Viewer, published on 12 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12271 in the wild and no public exploit code.

Affected product: jtermaat 360 Javascript Viewer. 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-2024-12271/ (Markdown: https://insights.sbomify.com/CVE-2024-12271/index.md)
```

## Sources

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

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