FKIE_CVE-2026-2899
Vulnerability from fkie_nvd - Published: 2026-03-05 04:15 - Updated: 2026-03-05 19:38
Severity ?
Summary
The Fluent Forms Pro Add On Pack plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.1.17. This is due to the `deleteFile()` method in the `Uploader` class lacking nonce verification and capability checks. The AJAX action is registered via `addPublicAjaxAction()` which creates both `wp_ajax_` and `wp_ajax_nopriv_` hooks. This makes it possible for unauthenticated attackers to delete arbitrary WordPress media attachments via the `attachment_id` parameter.
Note: The researcher described file deletion via the `path` parameter using `sanitize_file_name()`, but the actual code uses `Protector::decrypt()` for path-based deletion which prevents exploitation. The vulnerability is exploitable via the `attachment_id` parameter instead.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "The Fluent Forms Pro Add On Pack plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.1.17. This is due to the `deleteFile()` method in the `Uploader` class lacking nonce verification and capability checks. The AJAX action is registered via `addPublicAjaxAction()` which creates both `wp_ajax_` and `wp_ajax_nopriv_` hooks. This makes it possible for unauthenticated attackers to delete arbitrary WordPress media attachments via the `attachment_id` parameter.\r\n\r\nNote: The researcher described file deletion via the `path` parameter using `sanitize_file_name()`, but the actual code uses `Protector::decrypt()` for path-based deletion which prevents exploitation. The vulnerability is exploitable via the `attachment_id` parameter instead."
},
{
"lang": "es",
"value": "El plugin Fluent Forms Pro Add On Pack para WordPress es vulnerable a Autorizaci\u00f3n Faltante en todas las versiones hasta la 6.1.17, inclusive. Esto se debe a que el m\u00e9todo \u0027deleteFile()\u0027 en la clase \u0027Uploader\u0027 carece de verificaci\u00f3n de nonce y comprobaciones de capacidad. La acci\u00f3n AJAX se registra a trav\u00e9s de \u0027addPublicAjaxAction()\u0027, lo que crea los hooks \u0027wp_ajax_\u0027 y \u0027wp_ajax_nopriv_\u0027. Esto hace posible que atacantes no autenticados eliminen archivos adjuntos de medios de WordPress arbitrarios a trav\u00e9s del par\u00e1metro \u0027attachment_id\u0027.\n\nNota: El investigador describi\u00f3 la eliminaci\u00f3n de archivos a trav\u00e9s del par\u00e1metro \u0027path\u0027 usando \u0027sanitize_file_name()\u0027, pero el c\u00f3digo real usa \u0027Protector::decrypt()\u0027 para la eliminaci\u00f3n basada en la ruta, lo que evita la explotaci\u00f3n. La vulnerabilidad es explotable a trav\u00e9s del par\u00e1metro \u0027attachment_id\u0027 en su lugar."
}
],
"id": "CVE-2026-2899",
"lastModified": "2026-03-05T19:38:53.383",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 2.5,
"source": "security@wordfence.com",
"type": "Primary"
}
]
},
"published": "2026-03-05T04:15:57.233",
"references": [
{
"source": "security@wordfence.com",
"url": "https://fluentforms.com/docs/changelog/#3-toc-title"
},
{
"source": "security@wordfence.com",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/bb036338-abd7-4061-835d-038b765c68a6?source=cve"
}
],
"sourceIdentifier": "security@wordfence.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-862"
}
],
"source": "security@wordfence.com",
"type": "Primary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…