CVE-2022-45359
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 · uneditedUnauth. Arbitrary File Upload vulnerability in YITH WooCommerce Gift Cards premium plugin <= 3.19.0 on WordPress.
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 confidenceAn unauthenticated arbitrary file upload vulnerability exists in YITH WooCommerce Gift Cards premium plugin versions 3.19.0 and below for WordPress, allowing remote attackers to upload arbitrary files to the server without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.19.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 YITH WooCommerce Gift Cards plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'YITH WooCommerce Gift Cards' or 'Yith Woocommerce Gift Cards' in the plugin listAffected if The plugin appears in the installed plugins list and is activated
-
Identify the installed plugin versionIn the WordPress plugins list, locate YITH WooCommerce Gift Cards and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/yith-woocommerce-gift-cards/) for the version defined in the plugin header commentsAffected if The version shown is 3.19.0 or any version lower than 3.19.0
-
Verify the plugin is publicly accessibleCheck if the WordPress site is publicly accessible on the internet. Since this is an unauthenticated vulnerability, the vulnerable upload endpoint would be reachable without login credentialsAffected if The WordPress site is live and publicly accessible on the internet
-
Check for unexpected files on the serverReview the /wp-content/uploads/ directory (or custom upload directory) for any suspicious file types such as .php, .phtml, .exe, or other executable files that were not intentionally uploaded through legitimate WordPress media functionsAffected if Unexpected script files (.php, .phtml, etc.) exist in upload directories that were not intentionally placed there
If YITH WooCommerce Gift Cards plugin version 3.19.0 or lower is installed on a publicly accessible WordPress site, the environment is affected by this unauthenticated arbitrary file upload vulnerability.
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 the YITH WooCommerce Gift Cards premium plugin to a version newer than 3.19.0, or temporarily disable the plugin until a patch can be applied.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45359 — 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-2022-45359 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