A critical SQL injection vulnerability affecting the YMC Filter WordPress plugin has been added to the VulnCheck Known Exploited Vulnerabilities catalog. The flaw, tracked as CVE-2026-54836, carries a CVSS score of 9.3 and is categorized as an improper neutralization of special elements used in an SQL command, or CWE-89.
The vulnerability impacts all versions of the YMC Filter plugin from the initial release through version 3.11.5. By leveraging this flaw, an unauthenticated attacker can perform unauthorized SQL operations, potentially leading to the exposure of sensitive database information or other system compromises.
The vulnerability was officially published on June 25, 2026. According to tracking data, the flaw remained unlisted in major government-backed vulnerability catalogs for several months. As of late November 2026, the vulnerability does not appear in the Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities catalog, nor is it listed by the European Union Agency for Cybersecurity (ENISA).
The inclusion of CVE-2026-54836 in the VulnCheck KEV catalog on October 29, 2026, stems from reports of active exploitation in the wild. This listing occurred 126 days after the vulnerability was first disclosed. While the commercial research entity has identified the flaw as being actively exploited, this claim currently rests on a single source, and no other major vulnerability aggregator or government database has corroborated the active exploitation status at this time.
Public evidence regarding the exploitation of this plugin was first documented on October 29, 2026. Security researchers have linked the activity to the specific plugin version range mentioned above, noting that the nature of the flaw allows for remote, unauthenticated access.
Users of the YMC Filter plugin are advised to verify their current version and apply any available security updates provided by the developer. Because the vulnerability allows for direct interaction with the underlying database, administrators should also monitor their logs for signs of anomalous query patterns or unauthorized access attempts.
As of this reporting, the vendor has not released a statement confirming the exploitation attempts, and the information regarding active attacks remains based on external security research and threat intelligence monitoring. Organizations relying on this plugin should prioritize patching as a standard security precaution, regardless of the current status of corroborating reports from government agencies.





