# GHSA-phph-xpj4-wvcv: Cross-Site Scripting in hexo-admin

> Attackers with post creation privileges can execute arbitrary JavaScript in victims' browsers via unsanitized markdown in hexo-admin.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-phph-xpj4-wvcv?

GHSA-phph-xpj4-wvcv is a cross-site scripting vulnerability in hexo-admin, published on 3 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

All versions of `hexo-admin` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize rendered markdown, allowing attackers to execute arbitrary JavaScript in a victim's browser if they are able to create new posts.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-phph-xpj4-wvcv?

2 open source packages ship an affected version, including hexo-admin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hexo-admin` | npm | From 0.0.0 | None |
| `hexo-admin` | npm | From 0.0.0 | None |

## How do I fix GHSA-phph-xpj4-wvcv?

No fix has been published for GHSA-phph-xpj4-wvcv yet. Limit exposure of the affected software until one is available.

## Is GHSA-phph-xpj4-wvcv being exploited?

There is no known exploitation of GHSA-phph-xpj4-wvcv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-phph-xpj4-wvcv and fix it if it is affected.

What it is: GHSA-phph-xpj4-wvcv is a cross-site scripting vulnerability in hexo-admin, published on 3 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-phph-xpj4-wvcv in the wild and no public exploit code.

Affected packages and fixed versions:
- hexo-admin (npm): affected from 0.0.0; no fix listed
- hexo-admin (npm): affected from 0.0.0; no fix listed

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/GHSA-phph-xpj4-wvcv/ (Markdown: https://insights.sbomify.com/GHSA-phph-xpj4-wvcv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-phph-xpj4-wvcv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-phph-xpj4-wvcv/
Summaries are generated and may contain mistakes; the official description above is the record.