Strategic Overview
- Status
- Patched in 4.2.2
- Affected Plugin
- Atarim – AI Agency for WordPress: Edit Pages, Fix Code, Update Plugins, SEO & Client Feedback
- Affected Version
<= 4.2.1- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-60187
At a glance
CVE-2025-60187 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Atarim WordPress plugin, affecting versions <= 4.2.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.2.2; sites on affected versions should update now. Disclosed July 2025, reported by Denver Jackson.
Vulnerability Overview
The Visual Website Collaboration, Feedback & Project Management – Atarim plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 4.2.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Atarim <= 4.2.1 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Atarim the fix is 4.2.2: builds <= 4.2.1 are affected, anything from 4.2.2 onward is not.
Remediation
Update to version 4.2.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Atarim 4.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Atarim – AI Agency for WordPress: Edit Pages, Fix Code, Update Plugins, SEO & Client Feedback
- 9.8CVE-2025-60195: Atarim <= 4.2.1 Privilege Escalation
CVE-2025-60195 - 9.1Atarim - Client Interface <= 3.9.1 Missing Authorization
- 8.1CVE-2026-19942: Atarim <= 5.1.1 Arbitrary File Deletion
CVE-2026-19942 - 7.5CVE-2024-2038: Visual Website Collaboration Hardcoded Credentials
CVE-2024-2038 - 7.2CVE-2025-24570: Atarim <= 4.0.8 Stored Cross-Site Scripting
CVE-2025-24570 - 7.2CVE-2024-2793: Visual Website Collaboration Stored XSS
CVE-2024-2793 - 6.1CVE-2025-26993: Atarim <= 4.1.0 Reflected Cross-Site Scripting
CVE-2025-26993 - 6.1CVE-2023-47544: Atarim <= 3.12 Cross-Site Scripting
CVE-2023-47544
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C