Security readout for executives and security teams
Plain-English summary
AI Website Builder (GitHub build) 1.0.0 exposes powerful WordPress functions without authentication. An internet attacker could alter or delete content, install software, and upload files. If the server executes PHP from its uploads directory, this can become full remote code execution and complete site compromise.
Executive priority
Treat confirmed installations as an immediate remediation priority, especially on public sites. Potential outcomes include website takeover, malicious software installation, data destruction, and service disruption. Prioritize exposure discovery, containment, log review, and verification that uploads cannot execute PHP.
Technical view
The plugin’s REST routes lack authorization and nonce validation (CWE-862). Unauthenticated requests can install or activate plugins and themes, import attacker-controlled content, write arbitrary files under uploads, and delete content or media. Remote code execution depends on the hosting configuration allowing PHP execution from that directory.
Likely exposure
Exposure is limited to WordPress installations running the GitHub build of AI Website Builder version 1.0.0. Risk is highest when its REST routes are internet-accessible; impact escalates when PHP files execute from uploads. The sources do not establish other affected versions or distribution channels.
Exploitation context
The CVSS 3.1 score is 9.8, reflecting network access, low complexity, no privileges, and no user interaction. The bundle marks the issue as absent from KEV, and no cited evidence confirms active exploitation. WPScan is tagged as containing exploit information, which indicates public technical availability but not observed attacks.
Researcher notes
The decisive flaw is missing access control across privileged REST operations, not merely the conditional file-write-to-RCE path. Even without PHP execution in uploads, unauthenticated installation, activation, import, and deletion capabilities create severe integrity and availability risk. No patch version, vendor advisory, affected code details, or confirmed exploitation evidence appears in the bundle.
Mitigation direction
- Identify and disable or remove affected version 1.0.0 where operationally feasible.
- Restrict public access to the plugin’s REST routes until authoritative remediation is available.
- Prevent PHP execution within WordPress upload directories.
- Check vendor or project guidance for a fixed release or supported remediation.
- Preserve logs and investigate unexpected plugin, theme, upload, or deletion activity.
Validation and detection
- Inventory WordPress sites for the GitHub build of AI Website Builder 1.0.0.
- Confirm whether the affected REST routes are reachable without authentication.
- Verify that PHP execution is disabled in every uploads directory.
- Review recent plugin and theme installations, activations, uploads, imports, and deletions.
- After mitigation, confirm unauthenticated requests cannot invoke privileged plugin operations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-82923 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WPScanVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/663e7004-1cca-4c0f-8d54-7298d40fe179/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.