IP-DB.com
Türkçe English Deutsch Español
Entrar Obtener clave API
4.3Media

CVE-2024-13494WordPress File Upload <= 4.25.2 - Cross-Site Request Forgery in wfu_file_details

nickboss Iptanus File Upload Publicada: (hace 1 año)

Descripción

The WordPress File Upload plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.25.2. This is due to missing or incorrect nonce validation on the 'wfu_file_details' function. This makes it possible for unauthenticated attackers to modify user data details associated with uploaded files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Debilidad (CWE): CWE-352

Datos: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Se publican tal como los indican las fuentes, en inglés.

Productos y versiones afectados

FabricanteProductoVersiones
iptanus wordpress file upload < 4.25.3
nickboss Iptanus File Upload ≤ 4.25.2

Referencias y parches

Coincidencias CPE (NVD) (1)
  • cpe:2.3:a:iptanus:wordpress_file_upload:*:*:*:*:*:wordpress:*:* < 4.25.3

CVE recientes del mismo producto — WordPress plugins & themes

7.1Alta
CVE-2026-124969

Optimole <= 4.2.19 - Unauthenticated PHP Object Injection to Arbitrary File Deletion via 'comment_content'/'comment_agent' Parameter during Attachment Rename

optimole Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization

The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the replace_urls_in_value function in all versions up to, and…

9.8Crítica
CVE-2026-126173

AutomatorWP Pro Webhooks addon <= 1.4.4 - Missing Authorization to Unauthenticated Arbitrary User Password Reset / Account Takeover via Webhook with 'Is the user ID' Field

AutomatorWP AutomatorWP Webhooks

The AutomatorWP Pro plugin for WordPress' webhook addon is vulnerable to authorization bypass in all versions up to, and including, 1.4.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible …