CVE-2025-48140
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in metalpriceapi MetalpriceAPI metalpriceapi allows Code Injection.This issue affects MetalpriceAPI: from n/a through <= 1.1.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCode Injection vulnerability in the MetalpriceAPI library allows remote attackers to inject and execute arbitrary code due to improper control of code generation, likely through unsanitized user input being dynamically evaluated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if metalpriceapi library is installedRun 'pip show metalpriceapi' or inspect your project's dependency files (requirements.txt, pyproject.toml, Pipfile) for the metalpriceapi packageAffected if The library is not present in your environment means you are not affected
-
Identify installed versionRun 'pip show metalpriceapi' and record the Version number, then compare it against the version where the vulnerability was patchedAffected if You cannot determine the version or are running an unpatched version
-
Search for unsafe code execution in your codebaseGrep your project files for patterns like eval(), exec(), compile(), or similar functions being used with data that could originate from the metalpriceapi library or from user inputAffected if You find eval/exec calls that process data from this library or user-supplied values
-
Trace input flow to dynamic code functionsReview code paths where metalpriceapi is called and trace whether any user-provided or external data could reach eval(), exec(), or similar functionsAffected if Untrusted input can flow to dynamic code execution functions without sanitization
If the metalpriceapi library is installed and your codebase contains eval/exec patterns that handle library output or unvalidated user input, your environment may be affected by this code injection vulnerability
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of metalpriceapi if a patched version is available; otherwise, audit the codebase for unsafe code execution patterns (eval(), exec(), etc.) and implement strict input validation to prevent untrusted input from being interpreted as code.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data