Skip to main content
CVE-2026-125039VulnerabilityPublished

The EZ SQL Reports Shortcode Widget and DB Backup plugin for WordPress is vulnerable to Stored Cross-Site Scripting

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-125039· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 11:00 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
scheeeliEZ SQL Reports Shortcode Widget and DB BackupAffected
  • <=5.26.45
Fixed in–

AI-suggested

Until a fix is available, administrators should avoid publishing reports that include attacker-controlled data such as comment_agent or restrict access to such reports to trusted users only. Monitoring for updates from the plugin vendor is recommended.

Description

The EZ SQL Reports Shortcode Widget and DB Backup plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in all versions up to and including 5.26.45. This vulnerability arises from insufficient input sanitization and output escaping of the User-Agent header, which is stored in the comment_agent field. An unauthenticated attacker can inject malicious scripts that execute when a user accesses a page containing the injected report. Exploitation requires that an administrator saves a report with an SQL query selecting attacker-controlled data such as comment_agent and that the attacker knows the report's slug, which is easily obtained if the report is published publicly via the [SQLREPORT] shortcode.

References

Community reviews

Loading reviews…