Skip to main content
VulnerabilityPublished

CVE-2025-48140: MetalpriceAPI (WordPress plugin) · Code Injection

Affects MetalpriceAPI (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
metalpriceapi MetalpriceAPIAffected
  • <=1.1.4
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Restrict network access to MetalpriceAPI instances using firewalls and network segmentation to limit exposure to trusted IP addresses only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious input patterns indicative of code injection attempts. 3) Conduct thorough input validation and sanitization on all data entering the API, applying strict whitelisting where possible. 4) Monitor logs and network traffic for unusual activity or signs of exploitation attempts. 5) Run MetalpriceAPI with the least privileges necessary to limit the impact of a potential compromise. 6) Prepare for rapid patch deployment by establishing communication channels with the vendor or monitoring for updates. 7) Consider deploying runtime application self-protection (RASP) tools that can detect and block code injection attacks in real-time. 8) Perform regular security assessments and penetration testing focused on injection vulnerabilities in the API environment.

Description

Improper Control of Generation of Code ('Code Injection') vulnerability in metalpriceapi MetalpriceAPI allows Code Injection. This issue affects MetalpriceAPI: from n/a through 1.1.4.

References

Community reviews

Loading reviews…