Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-60114: CWE-94 Improper Control of Generation of Code ('Code Injection') in YayCommerce YayCurrency

0
Medium
VulnerabilityCVE-2025-60114cvecve-2025-60114cwe-94
Published: Fri Sep 26 2025 (09/26/2025, 08:31:31 UTC)
Source: CVE Database V5
Vendor/Project: YayCommerce
Product: YayCurrency

Description

Improper Control of Generation of Code ('Code Injection') vulnerability in YayCommerce YayCurrency allows Code Injection. This issue affects YayCurrency: from n/a through 3.2.

AI-Powered Analysis

AILast updated: 09/27/2025, 00:13:19 UTC

Technical Analysis

CVE-2025-60114 is a medium-severity vulnerability classified under CWE-94, which pertains to improper control of code generation, commonly known as code injection. This vulnerability affects the YayCurrency plugin developed by YayCommerce, specifically versions up to 3.2. YayCurrency is a plugin typically used in e-commerce platforms to handle currency conversion and display. The vulnerability allows an attacker with high privileges (PR:H) and no user interaction (UI:N) to inject and execute arbitrary code remotely over the network (AV:N). The vulnerability impacts confidentiality, integrity, and availability, albeit with limited confidentiality and integrity impact and a moderate availability impact, as indicated by the CVSS score of 6.6. The scope is changed (S:C), meaning the vulnerability can affect resources beyond the initially vulnerable component. The attack complexity is low (AC:L), indicating that exploitation does not require sophisticated conditions. However, the attacker must have high privileges, which typically means an authenticated user with elevated rights within the system. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability arises from improper sanitization or validation of code inputs within the plugin, allowing malicious code to be executed on the server, which could lead to unauthorized actions, data manipulation, or service disruption. Given the nature of the vulnerability, it is critical for administrators to monitor for updates and apply patches once available.

Potential Impact

For European organizations, especially those operating e-commerce platforms using YayCurrency, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized code execution on web servers, potentially compromising sensitive customer data, including payment information, user credentials, and transaction records. The integrity of pricing and currency conversion data could be manipulated, leading to financial losses or reputational damage. Availability could also be impacted if attackers disrupt services or deploy ransomware or other malicious payloads. Given the requirement for high privileges, the threat is more pronounced in environments where internal users or compromised accounts have elevated access. Organizations in Europe with strict data protection regulations such as GDPR could face legal and compliance repercussions if customer data is exposed or manipulated. The vulnerability could also be leveraged as a foothold for lateral movement within corporate networks, increasing the overall risk posture.

Mitigation Recommendations

1. Immediate mitigation involves restricting access to administrative interfaces of YayCurrency to trusted personnel only and enforcing strong authentication and authorization controls to minimize the risk of privilege escalation. 2. Conduct a thorough audit of user privileges and remove unnecessary high-level access rights. 3. Monitor logs for unusual activity indicative of code injection attempts or unauthorized access. 4. Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting code injection vectors. 5. Regularly update and patch the YayCurrency plugin as soon as official fixes are released by YayCommerce. 6. Employ input validation and sanitization best practices at the application level to prevent injection of malicious code. 7. Consider isolating the plugin environment or running it with minimal privileges to limit the impact of potential exploitation. 8. Educate administrators and developers about secure coding practices and the risks of code injection vulnerabilities.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:20:22.597Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d72b6179aa5c9d0854f46b

Added to database: 9/27/2025, 12:10:09 AM

Last enriched: 9/27/2025, 12:13:19 AM

Last updated: 10/7/2025, 1:33:35 PM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats