How severe is GHSA-vhqr-3gr2-7px9?

GHSA-vhqr-3gr2-7px9 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vhqr-3gr2-7px9?

GHSA-vhqr-3gr2-7px9 affects the following packages: intelliants/subrion (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vhqr-3gr2-7px9?

Update intelliants/subrion to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhqr-3gr2-7px9 is resolved across your whole dependency graph.

How do I detect GHSA-vhqr-3gr2-7px9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for intelliants/subrion. 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-vhqr-3gr2-7px9 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-vhqr-3gr2-7px9?

O3 pinpoints whether GHSA-vhqr-3gr2-7px9 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-vhqr-3gr2-7px9 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-vhqr-3gr2-7px9, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-vhqr-3gr2-7px9?

GHSA-vhqr-3gr2-7px9 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 88th 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.

When was GHSA-vhqr-3gr2-7px9 published, and has it been updated?

GHSA-vhqr-3gr2-7px9 was published on May 14, 2022 and was last updated on February 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-vhqr-3gr2-7px9

MEDIUM

Subrion CMS Cross-site Scripting

Also known asCVE-2018-14840

Published

May 14, 2022

Updated

Feb 17, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk88th percentile+0.60%

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.

Blast Radius

1 pkg affected

🐘intelliants/subrion

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

uploads/.htaccess in Subrion CMS 4.2.1 allows XSS because it does not block .html file uploads (but does block, for example, .htm file uploads).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`intelliants/subrion`	all versions	4.2.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-45150webappsphp

Subrion CMS 4.2.1 - Cross-Site Scripting

by Zeel Chavda · Aug 6, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for intelliants/subrion. 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 intelliants/subrion to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhqr-3gr2-7px9 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-vhqr-3gr2-7px9 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-vhqr-3gr2-7px9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`uploads/.htaccess` in Subrion CMS 4.2.1 allows XSS because it does not block .html file uploads (but does block, for example, .htm file uploads).

O3 Security · Impact-Aware SCA

Is GHSA-vhqr-3gr2-7px9 in your dependencies?

O3 detects GHSA-vhqr-3gr2-7px9 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