dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-4808

HIGH · 7.2 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Gerador de Certificados – DevApps plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the moveUploadedFile() function in all versions up to, and including, 1.3.6. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 · high confidence

The Gerador de Certificados – DevApps WordPress plugin versions up to 1.3.6 lack file type validation in the moveUploadedFile() function, allowing authenticated administrators to upload arbitrary files to the server. This arbitrary file upload can be leveraged for remote code execution.

MitigationUpdate the plugin to version 1.3.7 or later which includes proper file type validation. If immediate update is not possible, restrict administrator-level access and disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Gerador de Certificados - DevApps' or check the /wp-content/plugins/ directory for the plugin folder
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the plugin, and read the version number from the plugin details. Alternatively, check the main plugin PHP file for a version constant or the plugin header comment
    Affected if The version is lower than 1.3.7 or cannot be determined (treat as vulnerable)
  3. Check if administrator access is available
    Verify if any user account with administrator-level privileges exists on the WordPress site, or if the site allows administrator registration
    Affected if At least one authenticated administrator account can access the WordPress admin panel
  4. Verify the upload functionality is accessible
    Navigate to the plugin's certificate generation page (typically under a menu item like 'Gerador de Certificados' or 'Certificates') and locate any file upload or certificate upload feature
    Affected if The upload form exists and accepts file submissions from administrator users
  5. Confirm arbitrary file upload is possible (vulnerable condition)
    Using an administrator account, attempt to upload a non-image/non-PDF file (such as a .php file) through the plugin's upload form. If the file uploads without rejection or file type validation error, the vulnerability is present
    Affected if The upload accepts files without proper validation (no file type check, extension check, or MIME type validation)

The site is affected if the Gerador de Certificados - DevApps plugin is installed with a version lower than 1.3.7, an authenticated administrator can access the upload functionality, and the plugin permits uploading arbitrary file types without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.3.7 or later which includes proper file type validation. If immediate update is not possible, restrict administrator-level access and disable the plugin until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4808 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4808 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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