Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-374w-gwqr-fmxg — brotkrueml/schema

MEDIUM

GHSA-374w-gwqr-fmxg is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in brotkrueml/schema. A fix is available for brotkrueml/schema — see the affected versions and patch details below.

brotkrueml/schema fails to properly encode user input for output in HTML context, leading to XSS

Also known asCVE-2022-33154
Published
Jun 17, 2022
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-374w-gwqr-fmxg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐘brotkrueml/schema🐘brotkrueml/schema

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

The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistbrotkrueml/schema≥ 2.0.0&&< 2.5.12.5.1composer require brotkrueml/schema:^2.5.1
🐘Packagistbrotkrueml/schemaall versions1.13.1composer require brotkrueml/schema:^1.13.1

Affected Products

1 product · 2 configurations
Application
schemaschema_project
≥ 2.0.0 && < 2.5.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update brotkrueml/schema to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-374w-gwqr-fmxg is resolved across your whole dependency graph.

  3. 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

The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-374w-gwqr-fmxg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-374w-gwqr-fmxg: brotkrueml/schema | O3 Security