Unauthenticated local file disclosure via file inclusion
Published Apr 11, 2025 · Updated Apr 28, 2026
Local file inclusion in Foysal Imran IDonate 2.1.18 and earlier allows remote attackers to expose local file contents. Published advisories do not identify the request parameter, PHP file, or include/require call that accepts the attacker-controlled filename. The plugin must be active on a network-reachable WordPress site; no authentication is required, and the published consequence is local-file output.
Summary
What happened
Local file inclusion in Foysal Imran IDonate 2.1.18 and earlier allows remote attackers to expose local file contents. Published advisories do not identify the request parameter, PHP file, or include/require call that accepts the attacker-controlled filename. The plugin must be active on a network-reachable WordPress site; no authentication is required, and the published consequence is local-file output.
The record
- CVE
- CVE-2025-32519
- Published
- Apr 11, 2025
- Updated
- Apr 28, 2026
- Vendor
- Foysal Imran
- Product
- IDonate
- Classifications
- CWE-98, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.1.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo