How severe is GHSA-hwmc-r6mf-jh83?

No CVSS score has been assigned to GHSA-hwmc-r6mf-jh83 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hwmc-r6mf-jh83?

GHSA-hwmc-r6mf-jh83 affects the following packages: spatie/schema-org (Packagist), spatie/schema-org (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hwmc-r6mf-jh83?

Update spatie/schema-org to 3.23.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwmc-r6mf-jh83 is resolved across your whole dependency graph.

How do I detect GHSA-hwmc-r6mf-jh83 in my Packagist dependencies?

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

How do I mitigate GHSA-hwmc-r6mf-jh83 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-hwmc-r6mf-jh83 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hwmc-r6mf-jh83 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-hwmc-r6mf-jh83 published, and has it been updated?

GHSA-hwmc-r6mf-jh83 was published on July 1, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-hwmc-r6mf-jh83 — spatie/schema-org

Fix: spatie/schema-org#242

GHSA-hwmc-r6mf-jh83 is a security vulnerability in spatie/schema-org. A fix is available for spatie/schema-org — see the affected versions and patch details below.

Schema.org has cross-site scripting (XSS) via script break-out in toScript() output

Published

Jul 1, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

🐘spatie/schema-org🐘spatie/schema-org

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

Description

Schema.org has a cross-site scripting (XSS) vulnerability via script break-out in toScript() output.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`spatie/schema-org`	≥ 3.23.1&&< 3.23.2	3.23.2`composer require spatie/schema-org:^3.23.2`
🐘Packagist	`spatie/schema-org`	≥ 4.0.0&&< 4.0.2	4.0.2`composer require spatie/schema-org:^4.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spatie/schema-org, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update spatie/schema-org to 3.23.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwmc-r6mf-jh83 is resolved across your whole dependency graph.
Workarounds
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

Schema.org has a cross-site scripting (XSS) vulnerability via script break-out in toScript() output.

O3 Security · Impact-Aware SCA

Is GHSA-hwmc-r6mf-jh83 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works