Teddy Bear Customize Addon permits unauthenticated PHP upload
teddy-bear-customize-addon through 1.0.5 validates uploads using a client-supplied content type and preserves the original filename. An unauthenticated attacker can upload an arbitrary PHP file and execute code on the WordPress server. The authoritative export does not identify the upload endpoint, action, file parameter, or destination path.
- Component
- teddy-bear-customize-addon
- Plugin slug
teddy-bear-customize-addon- Affected
- <= 1.0.5
- Safe version
- See mitigation notes
- Published
- Sep 11, 2026
This CVE was published Sep 11, 2026 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
No fixed release is confirmed in the authoritative export. Deactivate the plugin until an upstream fix is available. The application-level fix must require authorization, validate file content and extension against a strict allowlist using server-side checks, generate a safe filename, and store uploads outside executable paths. Investigate the filesystem and rotate credentials if exploitation is suspected.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The teddy-bear-customize-addon WordPress plugin through 1.0.5 does not properly validate uploaded files, relying on a client-supplied content type and preserving the original filename, allowing unauthenticated attackers to upload arbitrary PHP files and execute code on the server.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H