What is CVE-2022-30999?

CVE-2022-30999 is a high-severity cross-site scripting (XSS) vulnerability in fof/upload (composer), affecting versions < 1.2.3. It is fixed in 1.2.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2022-30999?

CVE-2022-30999 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of fof/upload are affected by CVE-2022-30999?

fof/upload (composer) versions < 1.2.3 is affected.

Is there a fix for CVE-2022-30999?

Yes. CVE-2022-30999 is fixed in 1.2.3. Upgrade to this version or later.

Is CVE-2022-30999 exploitable, and should I be worried?

Whether CVE-2022-30999 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-30999 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-30999?

Upgrade fof/upload to 1.2.3 or later.

CVE-2022-30999 in fof/upload

Q: How severe is CVE-2022-30999?

CVE-2022-30999 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of fof/upload are affected by CVE-2022-30999?

fof/upload (composer) versions < 1.2.3 is affected.

Q: Is there a fix for CVE-2022-30999?

Yes. CVE-2022-30999 is fixed in 1.2.3. Upgrade to this version or later.

Q: Is CVE-2022-30999 exploitable, and should I be worried?

Whether CVE-2022-30999 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-30999 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-30999?

Upgrade fof/upload to 1.2.3 or later.

Summary

Possible cross-site scripting attack via unsanitized SVG files in FoF Upload

Workarounds

Upgrade to 1.2.3 (requires Flarum 1.2 or later), or remove the ability for users to upload SVG files through FoF Upload.

References

Thank you to Safwat Refaat for the responsible disclosure of this vulnerability.

Impact

If FoF Upload is configured to allow the uploading of SVG files (image/svg+xml), navigating directly to an SVG file URI could execute arbitrary Javascript code decided by an attacker.

This Javascript code could include the execution of HTTP web requests to Flarum, or any other web service. This could allow data to be leaked by an authenticated Flarum user, or, possibly, for data to be modified maliciously.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-30999 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.3); upgrading removes the vulnerable code path.

Affected versions

fof/upload (< 1.2.3)

Security releases

fof/upload → 1.2.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This has been patched with v1.2.3, which now sanitizes uploaded SVG files.

Frequently Asked Questions

What is CVE-2022-30999? CVE-2022-30999 is a high-severity cross-site scripting (XSS) vulnerability in fof/upload (composer), affecting versions < 1.2.3. It is fixed in 1.2.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2022-30999? CVE-2022-30999 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of fof/upload are affected by CVE-2022-30999? fof/upload (composer) versions < 1.2.3 is affected.
Is there a fix for CVE-2022-30999? Yes. CVE-2022-30999 is fixed in 1.2.3. Upgrade to this version or later.
Is CVE-2022-30999 exploitable, and should I be worried? Whether CVE-2022-30999 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-30999 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-30999? Upgrade fof/upload to 1.2.3 or later.