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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hwmc-r6mf-jh83 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-hwmc-r6mf-jh83?

O3 pinpoints whether GHSA-hwmc-r6mf-jh83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 July 1, 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

Fix: spatie/schema-org#242

GHSA-hwmc-r6mf-jh83 is a security vulnerability in spatie/schema-org. O3 Security confirms whether GHSA-hwmc-r6mf-jh83 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Published

Jul 1, 2026

Updated

Jul 1, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Jul 1, 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
🐘Packagist	`spatie/schema-org`	≥ 4.0.0&&< 4.0.2	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether GHSA-hwmc-r6mf-jh83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

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?

O3 detects GHSA-hwmc-r6mf-jh83 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works