Skip to main content
CVE-2025-13417VulnerabilityPublished

CVE-2025-13417: Plugin Organizer · SQL Injection

Affects Plugin OrganizerSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Plugin OrganizerAffected
  • =0
Fixed in–

AI-suggested

1. Immediate upgrade: Organizations should update the Plugin Organizer plugin to version 10.2.4 or later once available to ensure the vulnerability is patched. 2. Access control review: Restrict subscriber-level permissions to the minimum necessary and audit user roles to limit potential attackers. 3. Web application firewall (WAF): Deploy or update WAF rules to detect and block SQL injection attempts targeting the vulnerable parameter. 4. Input validation: Implement additional input validation and sanitization at the application or database layer as a temporary safeguard. 5. Monitoring and logging: Enhance monitoring of database queries and web application logs to detect anomalous activities indicative of SQL injection attempts. 6. Segmentation: Isolate WordPress instances and databases to limit the scope of potential compromise. 7. Incident response readiness: Prepare to respond to potential data breaches by having forensic and remediation plans in place. 8. Vendor communication: Engage with the plugin vendor for timely patch releases and security advisories. These steps go beyond generic advice by focusing on role-based access, WAF tuning, and operational readiness specific to this vulnerability.

Description

The Plugin Organizer WordPress plugin before 10.2.4 does not sanitize and escape a parameter before using it in a SQL statement, allowing subscribers to perform SQL injection attacks.

References

Community reviews

Loading reviews…