CVE-2026-32567
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 icopydoc YML for Yandex Market yml-for-yandex-market allows Path Traversal.This issue affects YML for Yandex Market: from n/a through < 5.3.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 confidencePath traversal vulnerability in the YML for Yandex Market WordPress plugin allows attackers to access files outside the restricted directory through improper path validation. The vulnerability exists in versions prior to 5.3.0 and can be exploited to read sensitive files on the server.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify YML for Yandex Market plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'YML for Yandex Market' in the list of active or installed plugins.Affected if Plugin is installed and active in WordPress
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on 'YML for Yandex Market' to view the plugin details, or check the plugin folder for a readme.txt or YML for Yandex Market.php file containing the version number.Affected if Version is displayed as lower than 5.3.0 or version information is unavailable (may indicate outdated plugin)
-
Confirm the plugin YML feed is accessibleAttempt to access the YML feed URL endpoint (commonly /yml-for-yandex-market/ or similar pattern based on plugin settings) via curl or browser request to verify the endpoint is active.Affected if YML feed endpoint responds successfully and plugin version is below 5.3.0
-
Inspect server logs for path traversal attemptsReview web server access logs (Apache error.log, Nginx access.log) for unusual requests containing '../' patterns targeting the plugin YML endpoint.Affected if Suspicious path traversal patterns found in logs targeting the plugin feed URL
If the YML for Yandex Market plugin is installed with a version prior to 5.3.0 and the YML feed feature is accessible, the environment is affected by this path traversal 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.
dbcve · scopedUpgrade to YML for Yandex Market version 5.3.0 or later which contains the path traversal fix. If immediate upgrade is not possible, restrict file access permissions and monitor for unauthorized file access attempts.
5.3.0 or later
- 1. Create a full backup of the WordPress site including database and files
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Find the 'YML for Yandex Market' plugin in the list
- 4. Click 'Update now' if an update is available, or manually upload version 5.3.0 or later
- 5. Verify the plugin updated successfully by checking the installed version
- 6. Test that the YML export functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32567 — 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-32567 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