Security readout for executives and security teams
Plain-English summary
Publicly reachable WordPress sites using Piotnet Addons For Elementor Pro version 7.1.67 or earlier may allow an unauthenticated attacker to upload arbitrary files. Successful abuse could compromise website data, content, and availability. The supplied sources do not identify a fixed version or confirm exploitation in the wild.
Executive priority
Treat this as an urgent internet-facing risk. Direct teams to inventory affected WordPress sites immediately, apply vendor-confirmed remediation, and investigate suspicious uploads. Prioritize public and business-critical sites. Critical severity supports rapid action, but the supplied evidence does not establish active exploitation or identify a fixed version.
Technical view
CVE-2026-28192 is classified as CWE-434, unrestricted upload of a dangerous file. It has CVSS 3.1 score 9.6 and vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. The description says authentication is not required, although the vector indicates user interaction is required. The supplied evidence does not explain that discrepancy or provide technical prerequisites.
Likely exposure
Exposure is most likely on internet-accessible WordPress installations running Piotnet Addons For Elementor Pro 7.1.67 or earlier. Actual risk depends on whether the vulnerable functionality is reachable and configured. The structured affected-product record is incomplete, listing versions as “n/a” and default status as unaffected, so inventory confirmation is essential.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. Nevertheless, unauthenticated arbitrary file upload can enable severe downstream compromise when uploaded content is executable or otherwise dangerous. No exploit steps, observed campaigns, or reliable exploitation prerequisites are provided.
Researcher notes
The record supports affected versions through 7.1.67 and CWE-434, but provides minimal technical detail. Note the tension between “unauthenticated” wording and CVSS UI:R, plus the affected entry’s “n/a” versions and default unaffected status. Avoid asserting exploitability conditions, upload endpoints, executable paths, or a patched version without additional vendor evidence.
Mitigation direction
- Identify every WordPress site using Piotnet Addons For Elementor Pro and record its installed version.
- Check Piotnet and Patchstack guidance for a fixed release; the supplied sources name no patch.
- Update to a vendor-confirmed safe version as soon as one is available.
- Disable or remove the plugin on exposed sites when prompt updating is unavailable.
- Restrict public access to affected sites where operationally feasible until remediation is confirmed.
Validation and detection
- Confirm whether Piotnet Addons For Elementor Pro is installed and whether its version is 7.1.67 or earlier.
- Verify the installed release against current Piotnet or Patchstack remediation guidance.
- Review web, WordPress, and security logs for unexpected upload activity or suspicious requests.
- Inspect writable upload locations for unexpected files, prioritizing executable or recently created content.
- After remediation, confirm the vulnerable plugin version is absent across production, staging, and backup-restored environments.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28192 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.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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:R/S:C/C:H/I:H/A:H2.86PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.