Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-14560 – Unauthenticated Arbitrary File Upload / Remote Code Execution – teddy-bear-customiz

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-14560 is a critical unauthenticated arbitrary file upload vulnerability (CWE-94, Code Injection) in the teddy-bear-customize-addon WordPress plugin. The plugin fails to validate uploaded files, trusting client-supplied content types and preserving original filenames, which allows an unauthenticated attacker to upload a malicious PHP file and achieve remote code execution on the underlying web server. The flaw carries the maximum CVSS v3.1 base score of 10.0.

Technical details

  • Root cause: The plugin’s file upload handler does not validate uploaded file content or restrict file extensions. It relies solely on a client-supplied Content-Type header and preserves the attacker-controlled original filename when storing the uploaded file.
  • Trigger conditions: An attacker submits a file upload request (e.g., via a teddy-bear customization/order form exposed by the plugin) containing a PHP payload disguised with a spoofed content type; no authentication or prior interaction with the site is required.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges (PR:N), no user interaction (UI:N) — the vulnerability can be exploited directly over HTTP/HTTPS against any site running the vulnerable plugin.
  • Impact: Successful exploitation results in arbitrary PHP code execution in the context of the web server, leading to full compromise of confidentiality, integrity, and availability of the affected WordPress site (scope changed, S:C).

Affected software

  • teddy-bear-customize-addon WordPress plugin — all versions up to and including 1.0.5

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No official patched version has been confirmed by the vendor at the time of publication. Site administrators should deactivate and remove the teddy-bear-customize-addon plugin until a verified fixed release is available, and monitor the plugin’s WordPress.org page for a security update.
  • If no patch is available:
    • Disable or restrict access to the plugin’s file/attachment upload endpoints at the web server or WAF layer.
    • Block uploads of files with executable extensions (.php, .phtml, .php5, etc.) regardless of declared content type, at the web server or reverse proxy.
    • Ensure the uploads directory used by the plugin is configured to prevent PHP execution (e.g., via .htaccess/web server rules).
    • Review server logs and the uploads directory for unexpected .php files or unfamiliar filenames as an indicator of exploitation.
    • Consider taking the affected functionality offline until the plugin can be updated or replaced.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge