How severe is GHSA-pc5g-j9j7-p4q3?

No CVSS score has been assigned to GHSA-pc5g-j9j7-p4q3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pc5g-j9j7-p4q3?

GHSA-pc5g-j9j7-p4q3 affects the following packages: calibreweb (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-pc5g-j9j7-p4q3?

No patched version of calibreweb has shipped for GHSA-pc5g-j9j7-p4q3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-pc5g-j9j7-p4q3 in my PyPI dependencies?

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

How do I mitigate GHSA-pc5g-j9j7-p4q3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pc5g-j9j7-p4q3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pc5g-j9j7-p4q3 can be triaged on real exposure rather than presence alone.

Is GHSA-pc5g-j9j7-p4q3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pc5g-j9j7-p4q3 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.

What is the EPSS score for GHSA-pc5g-j9j7-p4q3?

GHSA-pc5g-j9j7-p4q3 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pc5g-j9j7-p4q3?

GHSA-pc5g-j9j7-p4q3 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pc5g-j9j7-p4q3 published, and has it been updated?

GHSA-pc5g-j9j7-p4q3 was published on December 2, 2025 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-pc5g-j9j7-p4q3 — calibreweb

GHSA-pc5g-j9j7-p4q3 is a Cross-site Scripting (XSS) vulnerability in calibreweb. No vendor fix is recorded yet; mitigation options are listed below.

Calibre-Web Has a Stored Cross-Site Scripting (XSS) Vulnerability via the 'username' Field During User Creation

Also known asCVE-2025-65858PYSEC-2026-1234

Published

Dec 2, 2025

Updated

Jul 7, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pc5g-j9j7-p4q3.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍calibreweb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A Stored Cross-Site Scripting (XSS) vulnerability in Calibre-Web v0.6.25 allows attackers to inject malicious JavaScript into the 'username' field during user creation. The payload is stored unsanitized and later executed when the /ajax/listusers endpoint is accessed.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`calibreweb`	all versions	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 calibreweb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of calibreweb has shipped for GHSA-pc5g-j9j7-p4q3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pc5g-j9j7-p4q3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pc5g-j9j7-p4q3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-pc5g-j9j7-p4q3 in your dependencies?

O3 Security finds GHSA-pc5g-j9j7-p4q3 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works