CVE-2025-32519 Vulnerability Analysis & Exploit Details

CVE-2025-32519
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2025-32519 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-32519 Details

Status: Modified

Last updated: 🕔 01 Apr 2026, 17:22 UTC
Originally published on: 🕘 11 Apr 2025, 09:15 UTC

Time between publication and last update: 355 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2025-32519 Vulnerability Summary

CVE-2025-32519: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Foysal Imran IDonate idonate allows PHP Local File Inclusion.This issue affects IDonate: from n/a through <= 2.1.18.

Assessing the Risk of CVE-2025-32519

Access Complexity Graph

The exploitability of CVE-2025-32519 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-32519

With low attack complexity and no required privileges, CVE-2025-32519 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-32519, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-32519, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-32519 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-32519 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-32519 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-32519 References

External References

CWE Common Weakness Enumeration

CWE-98

CAPEC Common Attack Pattern Enumeration and Classification

  • PHP Remote File Inclusion CAPEC-193 In this pattern the adversary is able to load and execute arbitrary code remotely available from the application. This is usually accomplished through an insecurely configured PHP runtime environment and an improperly sanitized "include" or "require" call, which the user can then control to point to any web-accessible file. This allows adversaries to hijack the targeted application and force it to execute their own instructions.

Vulnerable Configurations

  • cpe:2.3:a:themeatelier:idonate:1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.7.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.7.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.8.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.8.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:1.9.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:1.9.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.0.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.0.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.0.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.0.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.0.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.0.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.0.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.0.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.0:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.0:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.1:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.1:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.2:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.2:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.3:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.3:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.4:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.4:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.5:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.5:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.6:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.6:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.7:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.7:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.8:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.8:*:*:*:*:wordpress:*:*
  • cpe:2.3:a:themeatelier:idonate:2.1.9:*:*:*:*:wordpress:*:*
    cpe:2.3:a:themeatelier:idonate:2.1.9:*:*:*:*:wordpress:*:*

Protect Your Infrastructure against CVE-2025-32519: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-40199 – Net::CIDR::Lite versions before 0.23 for Perl mishandles IPv4 mapped IPv6 addresses, which may allow IP ACL bypass. _pack_ipv6() includes the sent...
  • CVE-2026-40198 – Net::CIDR::Lite versions before 0.23 for Perl does not validate IPv6 group count, which may allow IP ACL bypass. _pack_ipv6() does not check that ...
  • CVE-2026-33119 – User interface (ui) misrepresentation of critical information in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofin...
  • CVE-2026-33118 – Microsoft Edge (Chromium-based) Spoofing Vulnerability
  • CVE-2026-5724 – The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configu...