How severe is GHSA-phph-xpj4-wvcv?

No CVSS score has been assigned to GHSA-phph-xpj4-wvcv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-phph-xpj4-wvcv?

GHSA-phph-xpj4-wvcv affects the following packages: hexo-admin (npm). Ecosystems affected: npm.

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

The records we use list no patched version of hexo-admin for GHSA-phph-xpj4-wvcv. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-phph-xpj4-wvcv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hexo-admin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-phph-xpj4-wvcv if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-phph-xpj4-wvcv actively exploited in the wild?

No public exploit code has been indexed for GHSA-phph-xpj4-wvcv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-phph-xpj4-wvcv published, and has it been updated?

GHSA-phph-xpj4-wvcv was published on September 3, 2020 and was last updated on September 29, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in hexo-adminGHSA-phph-xpj4-wvcv

GHSA-phph-xpj4-wvcv is a security vulnerability in hexo-admin. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Sep 3, 2020

Updated

Sep 29, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 29, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

hexo-adminnpm

411downloads / week

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hexo-admin`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hexo-admin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of hexo-admin for GHSA-phph-xpj4-wvcv. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-phph-xpj4-wvcv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works