CVE-2024-41951 is a medium-severity (CVSS 4.4) CWE-323 vulnerability in pheonixappapi. A fix is available for pheonixappapi — see the affected versions and patch details below.
PheonixAppAPI has visible Encoding Maps
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-41951.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2024-41951 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
pheonixappapiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This is a kind of moderate issue. The impact is not big for normal users but can be for users who want to secure their code/files/etc.
The issue is that the map of encoding/decoding languages are visible in code.
Patches
The Problem was patched in 0.2.5, so you should try to upgrade to the 0.2.5 version.
For 0.2.5 version users
Please run the post_install.py file inside the Scripts folder after downloading from pip.
Workarounds
There is a fix to this problem but it requires modifying the code. Modifying the code can lead to more issues.
References
There are currently no references to this problem.
NOTE: If you get a error regarding a function like -> get_key() or something like that, please re-run the file post_install.py inside Scripts folder
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pheonixappapi | all versions | 0.2.5pip install --upgrade 'pheonixappapi==0.2.5' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pheonixappapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pheonixappapi to 0.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41951 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 CVE-2024-41951 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-41951. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-41951 in your dependencies?
O3 Security finds CVE-2024-41951 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.