NVD / CVE Program· CNA WPScan

CVE-2021-24960: WordPress File Upload < 4.16.3 - Contributor+ Stored Cross-Site Scripting via Malicious SVG

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.67% (FIRST EPSS); higher than 52.3% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The WordPress File Upload WordPress plugin before 4.16.3, wordpress-file-upload-pro WordPress plugin before 4.16.3 allows users with a role as low as Contributor to configure the upload form in a way that allows uploading of SVG files, which could be then be used for Cross-Site Scripting attacks

MediumCVSS 5.4 · v3.1—No exploit No fix recorded

Published: Mar 7, 2022
Updated: Jun 16, 2026
EPSS: 0.6% · 52th percentile
CWE: CWE-434

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
iptanus	wordpress file upload	cpe:2.3:a:iptanus:wordpress_file_upload
iptanus	wordpress file upload pro	cpe:2.3:a:iptanus:wordpress_file_upload_pro

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

iptanus wordpress file uploadbefore 4.16.3
iptanus wordpress file upload probefore 4.16.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown WordPress File Upload
- 4.16.3 and later · before 4.16.3affected
Unknown wordpress-file-upload-pro
- 4.16.3 and later · before 4.16.3affected

Same product

iptanus: all records

Other highest-scoring records for the same primary product.

CVE-2024-9047WordPress File Upload <= 4.24.11 - Unauthenticated Path Traversal to Arbitrary File Read and Deletion in wfu_file_downloader.php
67This week
CVE-2020-10564An issue was discovered in the File Upload plugin before 4.13.0 for WordPress.
42Plan
CVE-2024-11613WordPress File Upload <= 4.24.15 - Unauthenticated Remote Code Execution, Arbitrary File Read, and Arbitrary File Deletion
40Plan

Published before and after this one in the same product

← EarlierCVE-2015-9339Aug 22, 2019 · The wp-file-upload plugin before 2.7.1 for WordPress has insufficient restrictions on upload of .js files.
30Monitor
← EarlierCVE-2015-9340Aug 22, 2019 · The wp-file-upload plugin before 3.0.0 for WordPress has insufficient restrictions on upload of php, js, pht, php3, php4, php5, phtml, htm,
30Monitor
Later →CVE-2021-24961Mar 7, 2022 · WordPress File Upload < 4.16.3 - Contributor+ Stored Cross-Site Scripting via Shortcode
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

plugins.trac.wordpress.orgchangeset 2677722

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

apple502j

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).