CVE-2026-22460
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in wpWax FormGent formgent allows Path Traversal.This issue affects FormGent: from n/a through <= 1.7.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe FormGent WordPress plugin versions 1.7.0 and below contain a path traversal vulnerability that allows attackers to manipulate file path references using directory traversal sequences (e.g., '../') to access files outside the intended restricted directory. This improper limitation of pathname to a restricted directory can lead to unauthorized file disclosure or access to sensitive system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm FormGent plugin installationLocate the wpWax FormGent plugin in your WordPress installation by checking the /wp-content/plugins/ directory for a folder named 'formgent' or similar variant. Access the WordPress admin dashboard and navigate to Plugins > Installed Plugins to verify FormGent is listed as an active or installed plugin.Affected if The FormGent plugin by wpWax is present in the WordPress plugins directory or listed in the admin panel.
-
Identify installed FormGent versionOpen the main plugin file (usually formgent.php or similar in the plugin folder) and locate the version comment/constant at the top of the file. Alternatively, check the plugin's readme.txt file for the 'Stable tag' version entry.Affected if The version number displayed is 1.7.0 or any version lower than 1.7.0.
-
Verify file handling functionality is accessibleReview the plugin settings and functionality to determine if any file upload, file import, or file retrieval features are enabled. These are the typical pathways where path traversal occurs. Check the WordPress admin panel for FormGent settings related to file handling or submissions.Affected if File handling or file processing features are enabled or accessible to users.
-
Inspect server logs for traversal attemptsExamine web server access logs (Apache, Nginx, or reverse proxy logs) for requests to FormGent endpoints that contain '../' sequences or unusual path patterns. Look for patterns like '..' encoded in various forms (%2e%2e/) in the request URL or parameters.
Your environment is affected if the wpWax FormGent plugin version is 1.7.0 or lower AND file handling features are enabled, allowing path manipulation through user-supplied input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of FormGent if available; otherwise, implement strict input validation that canonicalizes and validates file paths to reject traversal sequences, or disable the vulnerable functionality until a patch is released.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22460 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data