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

Back
New CVE Detected

CVE-2026-82923 – Unauthenticated RCE via Missing Authorization – AI Website Builder WordPress Plugin

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82923 is a critical Missing Authorization vulnerability (CWE-862) in the AI Website Builder WordPress plugin (GitHub build), version 1.0.0. The plugin exposes REST API routes with no authorization or nonce checks, allowing unauthenticated attackers to install/activate plugins and themes, import remote content, write arbitrary files to the uploads directory, and delete site content — the arbitrary file write can lead to full remote code execution on servers that execute PHP from the uploads folder. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin’s REST API endpoints do not verify caller authorization or validate a nonce before performing privileged actions.
  • Trigger conditions: Any unauthenticated user can send requests directly to the exposed REST routes; no credentials, prior session, or user interaction are required.
  • Attack vector: Network — remote, unauthenticated HTTP requests to the WordPress site’s REST API.
  • Impact: Installation/activation of arbitrary plugins and themes, import of attacker-controlled remote content, arbitrary file writes into the uploads directory, and deletion of site content/media. On hosts configured to execute PHP from the uploads directory, the file-write primitive results in remote code execution and full site compromise.

Affected software

  • AI Website Builder (GitHub build) — version 1.0.0 and earlier.
  • Note: the version distributed via the official WordPress.org plugin repository is reported as unaffected; only the GitHub-distributed build is impacted.

Severity

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

Mitigation and recommended actions

  • Immediate: No patched version of the plugin is currently available. Remove/uninstall the AI Website Builder (GitHub build) plugin from all affected WordPress sites immediately.
  • Additional cleanup: Uninstalling the plugin alone may not be sufficient — check for and manually remove any must-use plugin file and associated configuration option that may have been installed during the plugin’s activation.
  • Network mitigations: Until removal is confirmed, restrict or block external access to the plugin’s REST API routes (e.g., via WAF rules or web server access controls), and audit the uploads directory and site content/media for unauthorized changes, unfamiliar plugins/themes, or newly installed files.
  • Hardening: Configure servers to prevent PHP execution from the uploads directory to reduce the impact of any similar file-write issues.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/ai-website-builder/

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