CVE-2025-8417 json
Catalog Importer, Scraper & Crawler <= 5.1.4 - Unauthenticated PHP Code Injection
published 2025-09-11 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-27664
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
The Catalog Importer, Scraper & Crawler plugin for WordPress is vulnerable to PHP code injection in all versions up to, and including, 5.1.4. This is due to reliance on a guessable numeric token (e.g. ?key= 900001705) without proper authentication, combined with the unsafe use of eval() on user-supplied input. This makes it possible for unauthenticated attackers to execute arbitrary PHP code on the server via a forged request granted they can guess or brute-force the numeric key.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 13 mo ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- idiatech Catalog Importer, Scraper & Crawler
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3eb3533c-e33c-41db-b9cf-e9d71a0a5588?source=cve
- plugins.trac.wordpress.org /browser/intelligent-importer/tags/5.1.4/megaimporter.php#L57
- plugins.trac.wordpress.org /browser/intelligent-importer/tags/5.1.4/communication.php#L20
- plugins.trac.wordpress.org /browser/intelligent-importer/tags/5.1.4/communication.php#L244
- plugins.trac.wordpress.org /browser/intelligent-importer/tags/5.1.4/communication.php#L272
- plugins.trac.wordpress.org /browser/intelligent-importer/tags/5.1.4/communication.php#L300
Sources
- CVE List CVE-2025-8417
- NVD CVE-2025-8417
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.