dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-60114

MEDIUM · 6.6 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in YayCommerce YayCurrency yaycurrency allows Code Injection.This issue affects YayCurrency: from n/a through <= 3.3.1.

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 confidence

The YayCurrency plugin for WordPress (versions <= 3.3.1) contains a code injection vulnerability where improper control of code generation allows attackers to inject malicious code through the plugin's currency conversion or formatting functions.

MitigationUpdate YayCurrency to the latest version after checking vendor advisories, or disable the plugin if no patch is available; review server-side request validation and input sanitization in the plugin's currency handling functions.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm YayCurrency plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the yay-currency folder, or run: wp plugin list --name=yay-currency
    Affected if The yay-currency folder exists in the plugins directory
  2. Check installed YayCurrency version
    Open the main plugin file (yay-currency.php) and look for the 'Version' header in the plugin comments, or check readme.txt
    Affected if Installed version is 3.3.1 or lower (the vulnerable version range)
  3. Verify plugin is active
    Run: wp plugin status yay-currency or check the WordPress admin Plugins page
    Affected if Plugin status shows as 'Active' or 'Enabled'
  4. Confirm currency conversion or formatting features are in use
    Check WordPress options table for yay_currency settings, or review the plugin configuration in wp-admin for active currency conversion rules
    Affected if Currency conversion or formatting functions are enabled in the plugin settings

Environment is affected if YayCurrency plugin version 3.3.1 or lower is installed, active, and has currency conversion or formatting features configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update YayCurrency to the latest version after checking vendor advisories, or disable the plugin if no patch is available; review server-side request validation and input sanitization in the plugin's currency handling functions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60114 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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