What is CVE-2023-33175?

CVE-2023-33175 is a critical-severity security vulnerability in toui (pip), affecting versions >= 2.0.1, < 2.4.1. It is fixed in 2.4.1.

How severe is CVE-2023-33175?

CVE-2023-33175 has a CVSS score of 9.1 (Critical). 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 toui are affected by CVE-2023-33175?

toui (pip) versions >= 2.0.1, < 2.4.1 is affected.

Is there a fix for CVE-2023-33175?

Yes. CVE-2023-33175 is fixed in 2.4.1. Upgrade to this version or later.

Is CVE-2023-33175 exploitable, and should I be worried?

Whether CVE-2023-33175 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-2023-33175 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-2023-33175?

Upgrade toui to 2.4.1 or later.

CVE-2023-33175 in toui

Q: How severe is CVE-2023-33175?

CVE-2023-33175 has a CVSS score of 9.1 (Critical). 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 toui are affected by CVE-2023-33175?

toui (pip) versions >= 2.0.1, < 2.4.1 is affected.

Q: Is there a fix for CVE-2023-33175?

Yes. CVE-2023-33175 is fixed in 2.4.1. Upgrade to this version or later.

Q: Is CVE-2023-33175 exploitable, and should I be worried?

Whether CVE-2023-33175 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-2023-33175 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-2023-33175?

Upgrade toui to 2.4.1 or later.

Summary

toui allows user-specific variables to be shared between users

Workarounds

Do not use Website.user_vars in websites when using versions v2.0.1 to v2.4.0. Also, do not use Website.signin_user() in version v2.4.0 only.

Explanation

ToUI is using Flask-Caching (SimpleCache) to store user variables. My misunderstanding was that these caches are stored in the client's browser, but it seems that these are stored in the server side.

Impact

Websites that use Website.user_vars property in versions.

CVE-2023-33175 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. 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 (2.4.1); upgrading removes the vulnerable code path.

Affected versions

toui (>= 2.0.1, < 2.4.1)

Security releases

toui → 2.4.1 (pip)

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

It affects versions v2.0.1 to v2.4.0. Please upgrade to v2.4.1

Frequently Asked Questions

What is CVE-2023-33175? CVE-2023-33175 is a critical-severity security vulnerability in toui (pip), affecting versions >= 2.0.1, < 2.4.1. It is fixed in 2.4.1.
How severe is CVE-2023-33175? CVE-2023-33175 has a CVSS score of 9.1 (Critical). 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 toui are affected by CVE-2023-33175? toui (pip) versions >= 2.0.1, < 2.4.1 is affected.
Is there a fix for CVE-2023-33175? Yes. CVE-2023-33175 is fixed in 2.4.1. Upgrade to this version or later.
Is CVE-2023-33175 exploitable, and should I be worried? Whether CVE-2023-33175 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-2023-33175 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-2023-33175? Upgrade toui to 2.4.1 or later.