Skip to main content

GoDAM (WordPress plugin) CVE-2026-14282

| EUVDEUVD-2026-47919 CRITICAL
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-07-23 Wordfence GHSA-2cjr-xv2m-jcc3
9.8
CVSS 3.1 · Vendor: Wordfence
Share

Severity by source

Vendor (Wordfence) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
9.8 CRITICAL

Unauthenticated remote upload via a public form path (AV:N/PR:N/UI:N/AC:L) yielding webshell RCE gives full C/I/A impact; scope unchanged as code runs within the WordPress host.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 23, 2026 - 09:47 vuln.today
CVE Published
Jul 23, 2026 - 08:34 cve.org
CRITICAL 9.8

DescriptionCVE.org

The GoDAM - Organize WordPress Media Library & File Manager with Unlimited Folders for Images, Videos & more plugin for WordPress is vulnerable to arbitrary file uploads in versions up to, and including, 1.12.2. This is due to insufficient file type validation in the save_video_file() function hooked into WPForms' public wpforms_process_before_filter, which trusts the attacker-supplied multipart Content-Type header, preserves the original filename via wp_unique_filename(), and moves the raw upload with $wp_filesystem->move() into a web-served directory - bypassing wp_handle_upload()'s MIME/extension allowlist. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

AnalysisAI

Unauthenticated arbitrary file upload in the rtCamp GoDAM WordPress plugin (versions ≤ 1.12.2) allows remote attackers to plant executable files and likely achieve remote code execution. The flaw lives in the plugin's WPForms video-field integration, which bypasses WordPress's built-in upload sanitization by trusting the client-supplied Content-Type header and moving raw uploads into a web-served directory. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Identify public WPForms form with GoDAM video field
Delivery
Craft multipart upload with PHP payload and spoofed video/mp4 Content-Type
Exploit
Bypass MIME validation via save_video_file()
Execution
File moved to web-served directory with original name
Persist
Request uploaded shell URL
Impact
Execute arbitrary code on server

Vulnerability AssessmentAI

Exploitation Exploitation requires the target WordPress site to run the GoDAM plugin (≤ 1.12.2) alongside WPForms and to expose a public-facing form that includes GoDAM's custom video-upload field, since the vulnerable save_video_file() only executes via WPForms' wpforms_process_before_filter hook. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment All available signals point to genuine high priority rather than an inflated CVSS number. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An unauthenticated attacker locates a public WordPress form built with WPForms that includes a GoDAM video-upload field, then submits a multipart POST containing a PHP web shell whose Content-Type header is spoofed as video/mp4. Because save_video_file() trusts that header and preserves the original filename, the shell is moved intact into a web-accessible directory, and the attacker browses to its URL to execute commands on the server. …
Remediation Upgrade GoDAM to the fixed release beyond 1.12.2 as soon as it is available from the WordPress plugin repository; a corrective changeset is referenced upstream (https://plugins.trac.wordpress.org/changeset?reponame=&old=3607513%40godam&new=3607513%40godam), but no specific patched version string was provided in the input, so confirm the exact fixed version against the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/ce3ae202-1227-4247-9133-5c7284392c9f) before relying on it. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: disable the rtCamp GoDAM WordPress plugin on all affected installations (versions 1.12.2 and earlier); if the plugin is operationally critical, restrict network access to wp-admin and the plugin upload directories using firewall or WAF rules to block unauthenticated requests. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-14282 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy