CVE-2025-7686: CWE-352 Cross-Site Request Forgery (CSRF) in lmyoaoa weichuncai(WP伪春菜)
The weichuncai(WP伪春菜) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5. This is due to missing or incorrect nonce validation on the sm-options.php page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-7686 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability found in the weichuncai (WP伪春菜) WordPress plugin, affecting all versions up to and including 1.5. The vulnerability stems from missing or incorrect nonce validation on the sm-options.php administrative page. Nonces are security tokens used to verify that requests originate from legitimate users and not from forged sources. Without proper nonce validation, attackers can craft malicious requests that, when executed by an authenticated administrator (via clicking a malicious link or visiting a crafted webpage), cause unauthorized changes to plugin settings or injection of malicious web scripts. This can lead to persistent cross-site scripting (XSS) or other malicious payloads embedded within the site’s configuration, potentially compromising site integrity and user trust. The attack vector is remote and requires no authentication, but does require user interaction from an administrator. The vulnerability has a CVSS 3.1 base score of 6.1, indicating a moderate risk primarily due to the potential for limited confidentiality and integrity impacts, with no direct availability impact. No patches or official fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The plugin’s user base is likely niche but critical for affected sites, especially those managed by administrators who may be targeted via social engineering or phishing to trigger the CSRF attack.
Potential Impact
The primary impact of this vulnerability is unauthorized modification of plugin settings and potential injection of malicious scripts into affected WordPress sites. This can lead to compromised site integrity, defacement, or persistent cross-site scripting attacks that affect site visitors and administrators. Attackers could leverage this to escalate privileges, steal sensitive data, or pivot to further attacks within the hosting environment. Since the vulnerability requires an administrator to perform an action, social engineering risks are elevated. Organizations running websites with this plugin are at risk of unauthorized configuration changes that could disrupt normal operations or damage reputation. While availability is not directly impacted, the integrity and confidentiality of site data and administrative control are at risk. The lack of known exploits in the wild reduces immediate threat but does not eliminate risk, especially as attackers often develop exploits after vulnerability disclosure. The scope is limited to sites using this specific plugin, but given WordPress’s widespread use, the potential number of affected sites could be significant in regions where this plugin is popular.
Mitigation Recommendations
1. Immediately update the weichuncai (WP伪春菜) plugin to a version that includes proper nonce validation once available. Monitor vendor announcements for patches. 2. Until a patch is released, implement web application firewall (WAF) rules to detect and block suspicious POST requests to sm-options.php that lack valid nonce tokens or originate from untrusted sources. 3. Educate site administrators about the risks of clicking unknown or suspicious links, especially when logged into the WordPress admin panel. 4. Restrict administrative access to trusted IP addresses where feasible to reduce exposure. 5. Regularly audit plugin settings and site content for unauthorized changes or injected scripts. 6. Consider disabling or removing the plugin if it is not essential to reduce attack surface. 7. Employ Content Security Policy (CSP) headers to mitigate the impact of injected scripts. 8. Monitor logs for unusual activity related to administrative pages and investigate promptly. These steps go beyond generic advice by focusing on interim protective controls and administrator awareness until official patches are available.
Affected Countries
China, United States, Japan, South Korea, Germany, United Kingdom, India, Brazil, Russia, France
CVE-2025-7686: CWE-352 Cross-Site Request Forgery (CSRF) in lmyoaoa weichuncai(WP伪春菜)
Description
The weichuncai(WP伪春菜) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5. This is due to missing or incorrect nonce validation on the sm-options.php page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-7686 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability found in the weichuncai (WP伪春菜) WordPress plugin, affecting all versions up to and including 1.5. The vulnerability stems from missing or incorrect nonce validation on the sm-options.php administrative page. Nonces are security tokens used to verify that requests originate from legitimate users and not from forged sources. Without proper nonce validation, attackers can craft malicious requests that, when executed by an authenticated administrator (via clicking a malicious link or visiting a crafted webpage), cause unauthorized changes to plugin settings or injection of malicious web scripts. This can lead to persistent cross-site scripting (XSS) or other malicious payloads embedded within the site’s configuration, potentially compromising site integrity and user trust. The attack vector is remote and requires no authentication, but does require user interaction from an administrator. The vulnerability has a CVSS 3.1 base score of 6.1, indicating a moderate risk primarily due to the potential for limited confidentiality and integrity impacts, with no direct availability impact. No patches or official fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. The plugin’s user base is likely niche but critical for affected sites, especially those managed by administrators who may be targeted via social engineering or phishing to trigger the CSRF attack.
Potential Impact
The primary impact of this vulnerability is unauthorized modification of plugin settings and potential injection of malicious scripts into affected WordPress sites. This can lead to compromised site integrity, defacement, or persistent cross-site scripting attacks that affect site visitors and administrators. Attackers could leverage this to escalate privileges, steal sensitive data, or pivot to further attacks within the hosting environment. Since the vulnerability requires an administrator to perform an action, social engineering risks are elevated. Organizations running websites with this plugin are at risk of unauthorized configuration changes that could disrupt normal operations or damage reputation. While availability is not directly impacted, the integrity and confidentiality of site data and administrative control are at risk. The lack of known exploits in the wild reduces immediate threat but does not eliminate risk, especially as attackers often develop exploits after vulnerability disclosure. The scope is limited to sites using this specific plugin, but given WordPress’s widespread use, the potential number of affected sites could be significant in regions where this plugin is popular.
Mitigation Recommendations
1. Immediately update the weichuncai (WP伪春菜) plugin to a version that includes proper nonce validation once available. Monitor vendor announcements for patches. 2. Until a patch is released, implement web application firewall (WAF) rules to detect and block suspicious POST requests to sm-options.php that lack valid nonce tokens or originate from untrusted sources. 3. Educate site administrators about the risks of clicking unknown or suspicious links, especially when logged into the WordPress admin panel. 4. Restrict administrative access to trusted IP addresses where feasible to reduce exposure. 5. Regularly audit plugin settings and site content for unauthorized changes or injected scripts. 6. Consider disabling or removing the plugin if it is not essential to reduce attack surface. 7. Employ Content Security Policy (CSP) headers to mitigate the impact of injected scripts. 8. Monitor logs for unusual activity related to administrative pages and investigate promptly. These steps go beyond generic advice by focusing on interim protective controls and administrator awareness until official patches are available.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-07-15T18:54:22.324Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 689fff64ad5a09ad007439b9
Added to database: 8/16/2025, 3:47:48 AM
Last enriched: 2/26/2026, 4:28:15 PM
Last updated: 3/24/2026, 1:27:06 PM
Views: 115
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.