Security readout for executives and security teams
Plain-English summary
CVE-2026-22460 is a high-severity flaw in the WordPress FormGent plugin that may let an unauthenticated internet attacker delete files outside intended directories. Business impact is primarily availability: affected sites could break or lose critical files. Public sources do not show confirmed active exploitation.
Executive priority
Treat this as a prompt remediation item for any public WordPress site using FormGent. The main risk is site outage or disruption from file deletion. Prioritize inventory and plugin action, but avoid emergency claims unless exploitation is confirmed in your environment or trusted sources.
Technical view
The issue is CWE-22 path traversal in wpWax FormGent, described as arbitrary file deletion. CVSS 3.1 is 8.6: network reachable, low complexity, no privileges, no user interaction, high availability impact. The CVE description says FormGent through 1.7.0 is affected, though source metadata is limited and partly inconsistent.
Likely exposure
Public WordPress sites using the FormGent plugin at version 1.7.0 or earlier are the likely exposure. Sites not using FormGent are not indicated as affected. Evidence does not identify other products or platforms.
Exploitation context
The CVSS vector indicates remote, unauthenticated exploitation with low complexity and no user interaction. CISA KEV is false in the provided data, and no cited source confirms active exploitation. Do not assume exploitation is occurring without additional evidence.
Researcher notes
The source bundle has limited detail. It describes path traversal leading to arbitrary file deletion in FormGent through 1.7.0, while one Patchstack URL references 1.2.1. No exploit code, proof of concept, or fixed version is provided in the bundle. Validate against current vendor and Patchstack records.
Mitigation direction
- Inventory WordPress sites for the FormGent plugin and record installed versions.
- If FormGent is present at or below 1.7.0, check vendor and Patchstack guidance immediately.
- Update if a fixed version is available from trusted vendor channels.
- If no fix is available, disable or remove FormGent where business impact allows.
- Maintain current backups before making plugin or site changes.
- Restrict filesystem permissions for WordPress to the minimum required.
Validation and detection
- Confirm whether FormGent is installed on each WordPress site.
- Verify the installed FormGent version against CVE and Patchstack records.
- Check whether vendor guidance names a fixed version or workaround.
- Review site integrity for missing or unexpectedly changed files.
- Monitor web and application logs for unusual FormGent-related requests.
- Document affected assets, decisions, and remediation status.
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-22: 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-22460 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
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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.
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:C/C:N/I:N/A:H3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.