A security vulnerability affecting the DirectoryPress plugin for WordPress has been added to the VulnCheck Known Exploited Vulnerabilities (KEV) catalog. The flaw, tracked as CVE-2026-62032, was officially published on October 10, 2026, following its initial reservation on July 13, 2026.
According to data from the VulnCheck KEV, the vulnerability was first identified as being under active exploitation on November 7, 2026. This timeline indicates a period of 28 days between the vulnerability's public disclosure and the first recorded instance of its exploitation in the wild.
The claim of active exploitation currently rests on a single commercial research source. As of the latest reporting, the vulnerability does not appear in the CISA KEV catalog used by United States federal agencies, nor is it listed in the European Union’s ENISA vulnerability database. While the Computer Incident Response Center Luxembourg (CIRCL) aggregator also lists the exploit, it is considered an aggregator rather than an independent primary source and does not provide additional corroboration for the claim.
Public evidence regarding the exploitation of CVE-2026-62032 was first documented on November 7, 2026, via a report hosted on the Patchstack database. This report serves as the primary reference for the current exploitation status. However, the details surrounding the specific nature of the exploit and the mechanics of the attack remain unverified by independent parties.
The vulnerability has been assigned an Exploit Prediction Scoring System (EPSS) value of 1.5 percent, placing it in the 75th percentile of known vulnerabilities. Despite this ranking, the severity level for the flaw has not been officially categorized, and specific technical details regarding the nature of the security weakness remain limited.
Users of the DirectoryPress plugin are advised to monitor official security advisories for updates. Because the exploitation claim is based on a single source, organizations should prioritize standard patch management practices while awaiting further confirmation or technical analysis from security researchers. As of late November 2026, no further incidents or widespread campaigns linked to this specific CVE have been confirmed by major cybersecurity authorities.






