How severe is GHSA-4vrf-42cm-7xfw?

No CVSS score has been assigned to GHSA-4vrf-42cm-7xfw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4vrf-42cm-7xfw?

GHSA-4vrf-42cm-7xfw affects the following packages: tastyigniter/tastyigniter (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4vrf-42cm-7xfw?

The records we use list no patched version of tastyigniter/tastyigniter for GHSA-4vrf-42cm-7xfw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-4vrf-42cm-7xfw in my Packagist dependencies?

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

How do I mitigate GHSA-4vrf-42cm-7xfw 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-4vrf-42cm-7xfw actively exploited in the wild?

No public exploit code has been indexed for GHSA-4vrf-42cm-7xfw 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-4vrf-42cm-7xfw?

GHSA-4vrf-42cm-7xfw has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th 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-4vrf-42cm-7xfw?

GHSA-4vrf-42cm-7xfw is classified as Cross-site Scripting (XSS) (CWE-79), Unrestricted File Upload (CWE-434). These weakness types 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-4vrf-42cm-7xfw published, and has it been updated?

GHSA-4vrf-42cm-7xfw was published on October 20, 2025 and was last updated on October 20, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

TastyIgniter vulnerable to Cross-Site Scripting

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4vrf-42cm-7xfw.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘tastyigniter/tastyigniter

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

Cross-Site Scripting (XSS) vulnerability exists in TastyIgniter 3.7.7, affecting the /admin/media_manager component. Attackers can upload a malicious SVG file containing JavaScript code. When an administrator previews the file, the code executes in their browser context, allowing the attacker to perform unauthorized actions such as modifying the admin account credentials.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`tastyigniter/tastyigniter`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

tastyignitertastyigniter

1 version

3.7.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tastyigniter/tastyigniter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of tastyigniter/tastyigniter for GHSA-4vrf-42cm-7xfw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Cross-Site Scripting (XSS) vulnerability exists in TastyIgniter 3.7.7, affecting the /admin/media_manager component. Attackers can upload a malicious SVG file containing JavaScript code. When an administrator previews the file, the code executes in their browser context, allowing the attacker to perform unauthorized actions such as modifying the admin account credentials.

O3 Security · Impact-Aware SCA

Is GHSA-4vrf-42cm-7xfw in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

TastyIgniter vulnerable to Cross-Site ScriptingGHSA-4vrf-42cm-7xfw