Nickboss WordPress File Upload sensitive data exposure in plugin responses
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.5
- Who is exposed
- Not reported
Summary
The WordPress File Upload plugin by Nickboss (package wp-file-upload) exposes sensitive information in data it sends out. An attacker can retrieve that embedded sensitive data remotely, without logging in.
Written by a model
Original description
Insertion of Sensitive Information Into Sent Data vulnerability in Nickboss WordPress File Upload wp-file-upload allows Retrieve Embedded Sensitive Data.This issue affects WordPress File Upload: from n/a through 5.2.4.
What to do
Upgrade to a fixed version: 5.2.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131728 (WordPress WordPress File Upload plugin <= 5.2.4 - Sensitive Data Exposure vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131728 (entry last updated 2026-11-20):
Affected:
- Nickboss WordPress File Upload: fixed in 5.2.5
Fixed versions: 5.2.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131728 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131728 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/wp-file-upload/vulnerability/wordpress-wordpress-file-upload-plugin-5-2-4-sensitive-data-exposure-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131728
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131728"}.Affected versions
- wp-file-uploadfixed in 5.2.5 · through 5.2.4
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach17/20Affects WordPress (a widely deployed server, runtime, framework or database)
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131728 |
| Record | NVD · CVE-2026-131728 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/wp-file-upload/vulnerability/wordpress-wordpress-file-upload-plugin-5-2-4-sensitive-data-exposure-vulnerability?_s_id=cve |
Questions about CVE-2026-131728
Is CVE-2026-131728 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131728?
wp-file-upload: through 5.2.4 (fixed in 5.2.5).
Source: cve.now feed data
How do I fix CVE-2026-131728?
Upgrade to a fixed version: 5.2.5.
Source: cve.now feed data
Related
- CVE-2026-62071WordPress WordPress File Upload plugin <= 5.1.10 - SQL Injection vulnerability
- CVE-2026-66447WordPress WordPress File Upload plugin <= 5.1.7 - SQL Injection vulnerability
- CVE-2026-125822WordPress WordPress File Upload plugin <= 5.2.3 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-123460WordPress WordPress File Upload plugin <= 5.2.2 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-66570WordPress WordPress File Upload plugin <= 5.2.1 - Cross Site Scripting (XSS) vulnerability
- CVE-2023-2688WordPress File Upload / WordPress File Upload Pro <= 4.19.1 - Authenticated (Administrator+) Path Traversal
No corrections so far. Something wrong on this page? Report an error.