VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

YML for Yandex Market <= 5.10.0 — Unauthenticated Sensitive Information Exposure through Log File via 'y4ym_check_action' Parameter via admin-post.php

CVE-2026-120548Published · Updated

Action summary

Affected: ≤5.10.0Update to 5.11.0 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-532 Insertion of Sensitive Information into Log File
Required access
No account needed
Exploit prediction (EPSS)
0.3% chance in 30 days24th percentile
CISA KEV
Not listed
On this page8

Am I affected?

YML for Yandex Market yml-for-yandex-market

  1. Affected≤ 5.10.0
  2. Patched in5.11.0

Update to 5.11.0 or newer.

You are affected if you run ≤ 5.10.0. Version 5.11.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under YML for Yandex Market.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 5.11.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch YML for Yandex Market to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Kuba.

The YML for Yandex Market plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.10.0 via the 'y4ym_check_action' parameter. This makes it possible for unauthenticated attackers to extract the merchant's plaintext Yandex Market API key written to the publicly accessible log file at wp-content/uploads/y4ym/yml-for-yandex-market.log, granting full control over the merchant's marketplace catalogue, prices, and stock. Exploitation requires that the targeted feed has a stored Yandex Market API key and that the y4ym_keeplogs option is enabled — both conditions that represent normal, documented plugin usage actively encouraged by the plugin's own support and feedback workflow.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in YML for Yandex Market

All 6
More vulnerabilities in YML for Yandex Market
SeverityVulnerabilityCVEPublished
Medium6.5Authenticated (Shop Manager+) Arbitrary File Deletion
<5.3.0Update to 5.3.0
CVE-2026-32567
High7.2Authenticated (Shop Manager+) Remote Code Execution
<5.0.26Update to 5.0.26
CVE-2025-14545
Medium6.1Reflected Cross-Site Scripting
≤4.7.2Update to 4.7.3
CVE-2024-9378
Medium6.1Reflected Cross-Site Scripting
≤4.2.3Update to 4.2.4
CVE-2024-1365
Medium6.1Reflected Cross-Site Scripting
<3.10.8Update to 3.10.8
CVE-2023-30473

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?