How severe is GHSA-f3rf-v9qm-9c89?

No CVSS score has been assigned to GHSA-f3rf-v9qm-9c89 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f3rf-v9qm-9c89?

GHSA-f3rf-v9qm-9c89 affects the following packages: in2code/femanager (Packagist), in2code/femanager (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f3rf-v9qm-9c89?

Update in2code/femanager to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3rf-v9qm-9c89 is resolved across your whole dependency graph.

How do I detect GHSA-f3rf-v9qm-9c89 in my Packagist dependencies?

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

How do I mitigate GHSA-f3rf-v9qm-9c89 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-f3rf-v9qm-9c89?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f3rf-v9qm-9c89 can be triaged on real exposure rather than presence alone.

Is GHSA-f3rf-v9qm-9c89 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-f3rf-v9qm-9c89, including 2 in-the-wild exploitations 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-f3rf-v9qm-9c89?

GHSA-f3rf-v9qm-9c89 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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-f3rf-v9qm-9c89?

GHSA-f3rf-v9qm-9c89 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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-f3rf-v9qm-9c89 published, and has it been updated?

GHSA-f3rf-v9qm-9c89 was published on September 1, 2021 and was last updated on December 2, 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

Not in CISA KEV

GHSA-f3rf-v9qm-9c89 — in2code/femanager

Fix: in2code-de/femanager@70f873c

GHSA-f3rf-v9qm-9c89 is a Cross-site Scripting (XSS) vulnerability in in2code/femanager. 2 public exploit references exist, so weaponization risk is real. A fix is available for in2code/femanager — see the affected versions and patch details below.

Cross-site Scripting in the femanager TYPO3 extension

Also known asCVE-2021-36787

Published

Sep 1, 2021

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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.

Real-World Exposure

2 pkgs affected

🐘in2code/femanager🐘in2code/femanager

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

Note: If SVG uploads are required, it is recommended to use the TYPO3 extension svg_sanitizer (added to TYPO3 core since versions 9.5.28, 10.4.18 and 11.3.0) to prevent upload of malicious SVG files or to set up a strict Content Security Policy for the destination folder of uploaded images.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/femanager`	all versions	5.5.1`composer require in2code/femanager:^5.5.1`
🐘Packagist	`in2code/femanager`	≥ 6.0.0&&< 6.3.1	6.3.1`composer require in2code/femanager:^6.3.1`

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.

The femanager extension before 5.5.1 and 6.x before 6.3.1 for TYPO3 allo…

seclists.orgNVDFeb 2022

The femanager extension before 5.5.1 and 6.x before 6.3.1 for TYPO3 allo…

packetstormsecurity.comNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/femanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/femanager to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3rf-v9qm-9c89 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f3rf-v9qm-9c89 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f3rf-v9qm-9c89. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The extension allows by default to upload SVG files when a logged in frontend user uploads a new profile image. This may lead to Cross-Site Scripting, when the uploaded SVG image is used as is on the website. Note: If SVG uploads are required, it is recommended to use the TYPO3 extension svg_sanitizer (added to TYPO3 core since versions 9.5.28, 10.4.18 and 11.3.0) to prevent upload of malicious SVG files or to set up a strict Content Security Policy for the destination folder of uploaded images.

O3 Security · Impact-Aware SCA

Is GHSA-f3rf-v9qm-9c89 in your dependencies?

O3 Security finds GHSA-f3rf-v9qm-9c89 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works