Skip to main content
VulnerabilityPublished

CVE-2026-125822: Nickboss WordPress File Upload · Cross-site Scripting

Affects Nickboss WordPress File UploadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 5.2.4 soon.

Data as of 15 Nov 2026, 19:08 UTC

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

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.17.1
Patch
Available – fixed in 5.2.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 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 14 Nov 2026.

What to do

Upgrade Nickboss WordPress File Upload to 5.2.4.

Affected software

ProductAffectedFixed in
WordPress File Uploadwp-file-uploadAffected
  • <5.2.4
Fixed in
  • 5.2.4

AI-suggested

Upgrade the Nickboss WordPress File Upload plugin to version 5.2.4 or later, where this vulnerability is fixed. No other mitigation is required as the vendor has provided an official fix.

Description

CVE-2026-125822 is a stored cross-site scripting (XSS) vulnerability in the Nickboss WordPress File Upload plugin versions prior to 5.2.4. The flaw arises from improper neutralization of input during web page generation, allowing attackers to inject malicious scripts that can execute in the context of users viewing the affected pages. This vulnerability affects versions from initial release up to 5.2.3 and has been assigned a high severity rating with a CVSS score of 7.1. The issue is fixed in version 5.2.4.

References

Community reviews

Loading reviews…