CVE-2025-63049: 
WordPress vulnerability analysis and mitigation

CVE-2025-63049 is a Missing Authorization vulnerability in the CridioStudio ListingPro Lead Form WordPress plugin (listingpro-lead-form) that allows unauthenticated network-based attackers to access functionality not properly constrained by access control lists (ACLs). The vulnerability affects all versions of the plugin through 1.0.7 (with some sources citing through 1.0.2). It was published on December 9, 2025, and assigned by Patchstack. The CVSS v3.1 base score is 5.3 (Medium) (Feedly, EUVD).

The root cause is classified as CWE-862 (Missing Authorization), meaning the plugin fails to verify whether a requesting user has the appropriate permissions before granting access to certain functionality. The attack vector is network-based, requires no authentication, no user interaction, and low attack complexity, making it trivially exploitable by any remote attacker. The specific unprotected functionality or endpoints have not been publicly detailed in available sources, but the vulnerability class typically involves WordPress REST API endpoints or AJAX actions lacking capability checks (Feedly, EUVD).

Successful exploitation results in a low integrity impact with no confidentiality or availability impact, meaning attackers can perform unauthorized actions — such as submitting or manipulating lead form data — without proper authentication. The scope is unchanged, limiting the blast radius to the affected plugin's functionality. While not a critical-severity issue, unauthorized manipulation of lead form submissions could affect business data integrity on affected WordPress sites (Feedly).

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been identified for CVE-2025-63049. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.04%, indicating a very low probability of exploitation in the near term (Feedly).

Users of the ListingPro Lead Form WordPress plugin should update to a version beyond 1.0.7 if a patched release is available from CridioStudio. If no patched version is yet available, site administrators should consider deactivating or removing the plugin until a fix is released. Monitoring WordPress access logs for unexpected or unauthorized requests to plugin-related endpoints is also advisable as a compensating control (Feedly, EUVD).