CVE-2026-49779
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 · uneditedPath Traversal: '.../...//' vulnerability in Addify Tax Exempt for WooCommerce allows Path Traversal. This issue affects Tax Exempt for WooCommerce: from n/a before 1.9.5.
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 Addify Tax Exempt for WooCommerce plugin before version 1.9.5 contains a path traversal vulnerability exploitable via the '.../...//' pattern. This allows attackers to access files outside the web root directory through improper input validation of file paths.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check the installed plugin versionNavigate to WordPress Admin > Plugins > Tax Exempt for WooCommerce and note the version number displayed, or use wp-cli: wp plugin list --name='tax-exempt-for-woocommerce' --format=jsonAffected if The installed version is 1.9.3 or lower
-
Identify customer input fields used by the pluginReview the plugin settings pages in WooCommerce > Tax Exempt and identify any fields that accept customer-provided data such as names, addresses, or tax IDsAffected if The plugin accepts customer input in any fields that could be processed server-side
-
Verify if directory traversal characters are filteredTemporarily submit a test value containing '../' sequences in the plugin's customer-facing input fields (such as during a test checkout or exempt certificate upload) and observe if the input is accepted without sanitization or rejectionAffected if The plugin accepts '../' characters without blocking or sanitizing them
-
Review plugin source code for file access functionsIf you have file system access, examine the plugin files in wp-content/plugins/tax-exempt-for-woocommerce/ for functions that handle file operations (fopen, file_get_contents, include, require) using customer-supplied input without validationAffected if The plugin code uses customer input in file operations without validating for '../' sequences
Your environment is affected if the Tax Exempt for WooCommerce plugin version is 1.9.3 or lower AND customer-facing input fields accept '../' directory traversal sequences without sanitization.
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 dataUpgrade to version 1.9.5 or later which includes proper path traversal protection. Until then, restrict admin access and monitor for suspicious path-based requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49779 — 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-49779 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