EnvialosimpleWordPress extension · Donweb
CVE-2024-2125
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe EnvíaloSimple: Email Marketing y Newsletters plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.3. This is due to missing or incorrect nonce validation on the gallery_add function. This makes it possible for unauthenticated attackers to upload malicious files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The Cross-Site Request Forgery was patched in 2.4, however, nothing was done about the ability to upload arbitrary files.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe EnvíaloSimple WordPress plugin versions up to 2.3 contain a CSRF vulnerability in the gallery_add function due to missing nonce validation. This allows unauthenticated attackers to forge administrative actions via social engineering. Although version 2.4 patches the CSRF, the underlying arbitrary file upload capability remains exploitable, creating a separate file upload vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
EnvialosimpleWordPress extension
< 2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify EnvíaloSimple plugin installationCheck WordPress wp-content/plugins directory for envialosimple folder, or view installed plugins list in WordPress admin under PluginsAffected if Plugin folder named envialosimple or envialo-simple is present on the server
-
Confirm installed version numberRead the main plugin PHP file header for 'Version:' value, or check the plugin readme.txt fileAffected if Version read from the plugin header is less than 2.4
-
Locate gallery_add function in plugin codeSearch plugin source files for 'function gallery_add' or 'gallery_add' action hook to verify the vulnerable function existsAffected if Function gallery_add is found in the plugin code without nonce validation checks
-
Identify file upload handlingSearch plugin code for file upload related functions (wp_handle_upload, move_uploaded_file, or $_FILES usage) within gallery or upload related filesAffected if File upload code exists without proper file type validation or upload restrictions
User is affected if the EnvíaloSimple plugin is installed with version < 2.4 and the gallery_add function or unrestricted file upload capability is present in the code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.4
Update to version 2.4+ for CSRF protection, but note that the arbitrary file upload issue persists in version 2.4 - the plugin code requires additional hardening for proper file type validation and upload restrictions.
Fix this in Envialosimple
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2125 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data