CVE-2022-3850: CWE-352 Cross-Site Request Forgery (CSRF) in Unknown Find and Replace All
The Find and Replace All WordPress plugin before 1.3 does not have CSRF check when replacing string, which could allow attackers to make a logged admin replace arbitrary string in database tables via a CSRF attack
AI Analysis
Technical Summary
CVE-2022-3850 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WordPress plugin "Find and Replace All" prior to version 1.3. This plugin facilitates bulk string replacement operations within WordPress database tables. The vulnerability arises because the plugin lacks proper CSRF protections when performing the replace string action. Specifically, it does not verify the authenticity of requests that trigger string replacements, allowing an attacker to craft malicious web requests that, when executed by an authenticated administrator, can cause arbitrary string replacements in the database without the administrator's explicit consent. The vulnerability requires the victim to be logged in as an administrator and to interact with a maliciously crafted web page or link that triggers the CSRF attack. The impact of this vulnerability is limited to integrity, as it allows unauthorized modification of database content but does not directly affect confidentiality or availability. The CVSS 3.1 base score is 4.3 (medium severity), reflecting that the attack vector is network-based, requires user interaction, and no privileges are needed beyond an authenticated admin session. No known exploits have been reported in the wild, and no official patches or updates are linked, though upgrading to version 1.3 or later presumably addresses the issue. Since the plugin is used within WordPress environments, the scope of affected systems includes websites that utilize this plugin version, particularly those with administrative users who might be targeted via social engineering or malicious sites to trigger the CSRF. The vulnerability is typical of web applications that fail to implement anti-CSRF tokens or similar protections on sensitive state-changing operations.
Potential Impact
For European organizations, the primary impact of this vulnerability lies in the potential unauthorized modification of website content or database entries managed via the affected plugin. This could lead to data integrity issues, such as altering site text, links, or configuration data stored in the database, potentially undermining trustworthiness or causing functional disruptions. While it does not directly expose sensitive data or cause denial of service, manipulated content could be used to mislead users, inject malicious links, or disrupt business operations relying on accurate website content. Organizations with public-facing WordPress sites using this plugin are at risk, especially if administrators are targeted through phishing or social engineering to trigger the CSRF. The impact is more pronounced for sectors where website content integrity is critical, such as e-commerce, government portals, and financial services. Additionally, compromised content could indirectly facilitate further attacks, such as phishing or malware distribution, increasing the overall risk profile.
Mitigation Recommendations
1. Immediate upgrade: Organizations should verify the version of the Find and Replace All plugin in use and upgrade to version 1.3 or later, where the CSRF vulnerability is addressed. 2. Implement Web Application Firewall (WAF) rules: Deploy WAF rules that detect and block suspicious CSRF attempts, especially those targeting administrative endpoints of WordPress plugins. 3. Enforce strict administrator session management: Use multi-factor authentication (MFA) for admin accounts to reduce the risk of session hijacking or unauthorized access. 4. Educate administrators: Conduct awareness training to recognize phishing and social engineering attempts that could lead to CSRF exploitation. 5. Monitor logs: Regularly audit web server and application logs for unusual POST requests or unexpected database changes that could indicate exploitation attempts. 6. Use security plugins: Employ WordPress security plugins that add CSRF protections or monitor for unauthorized changes. 7. Limit plugin usage: Evaluate the necessity of the Find and Replace All plugin and remove it if not essential, reducing the attack surface. 8. Harden WordPress installations: Ensure WordPress core and all plugins/themes are kept up to date, and disable unused plugins to minimize vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Austria
CVE-2022-3850: CWE-352 Cross-Site Request Forgery (CSRF) in Unknown Find and Replace All
Description
The Find and Replace All WordPress plugin before 1.3 does not have CSRF check when replacing string, which could allow attackers to make a logged admin replace arbitrary string in database tables via a CSRF attack
AI-Powered Analysis
Technical Analysis
CVE-2022-3850 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the WordPress plugin "Find and Replace All" prior to version 1.3. This plugin facilitates bulk string replacement operations within WordPress database tables. The vulnerability arises because the plugin lacks proper CSRF protections when performing the replace string action. Specifically, it does not verify the authenticity of requests that trigger string replacements, allowing an attacker to craft malicious web requests that, when executed by an authenticated administrator, can cause arbitrary string replacements in the database without the administrator's explicit consent. The vulnerability requires the victim to be logged in as an administrator and to interact with a maliciously crafted web page or link that triggers the CSRF attack. The impact of this vulnerability is limited to integrity, as it allows unauthorized modification of database content but does not directly affect confidentiality or availability. The CVSS 3.1 base score is 4.3 (medium severity), reflecting that the attack vector is network-based, requires user interaction, and no privileges are needed beyond an authenticated admin session. No known exploits have been reported in the wild, and no official patches or updates are linked, though upgrading to version 1.3 or later presumably addresses the issue. Since the plugin is used within WordPress environments, the scope of affected systems includes websites that utilize this plugin version, particularly those with administrative users who might be targeted via social engineering or malicious sites to trigger the CSRF. The vulnerability is typical of web applications that fail to implement anti-CSRF tokens or similar protections on sensitive state-changing operations.
Potential Impact
For European organizations, the primary impact of this vulnerability lies in the potential unauthorized modification of website content or database entries managed via the affected plugin. This could lead to data integrity issues, such as altering site text, links, or configuration data stored in the database, potentially undermining trustworthiness or causing functional disruptions. While it does not directly expose sensitive data or cause denial of service, manipulated content could be used to mislead users, inject malicious links, or disrupt business operations relying on accurate website content. Organizations with public-facing WordPress sites using this plugin are at risk, especially if administrators are targeted through phishing or social engineering to trigger the CSRF. The impact is more pronounced for sectors where website content integrity is critical, such as e-commerce, government portals, and financial services. Additionally, compromised content could indirectly facilitate further attacks, such as phishing or malware distribution, increasing the overall risk profile.
Mitigation Recommendations
1. Immediate upgrade: Organizations should verify the version of the Find and Replace All plugin in use and upgrade to version 1.3 or later, where the CSRF vulnerability is addressed. 2. Implement Web Application Firewall (WAF) rules: Deploy WAF rules that detect and block suspicious CSRF attempts, especially those targeting administrative endpoints of WordPress plugins. 3. Enforce strict administrator session management: Use multi-factor authentication (MFA) for admin accounts to reduce the risk of session hijacking or unauthorized access. 4. Educate administrators: Conduct awareness training to recognize phishing and social engineering attempts that could lead to CSRF exploitation. 5. Monitor logs: Regularly audit web server and application logs for unusual POST requests or unexpected database changes that could indicate exploitation attempts. 6. Use security plugins: Employ WordPress security plugins that add CSRF protections or monitor for unauthorized changes. 7. Limit plugin usage: Evaluate the necessity of the Find and Replace All plugin and remove it if not essential, reducing the attack surface. 8. Harden WordPress installations: Ensure WordPress core and all plugins/themes are kept up to date, and disable unused plugins to minimize vulnerabilities.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- WPScan
- Date Reserved
- 2022-11-03T12:49:07.162Z
- Cisa Enriched
- true
Threat ID: 682d983ec4522896dcbf03a1
Added to database: 5/21/2025, 9:09:18 AM
Last enriched: 6/24/2025, 12:56:52 PM
Last updated: 7/23/2025, 6:45:13 PM
Views: 8
Related Threats
CVE-2025-23289: CWE-532 Insertion of Sensitive Information into Log File in NVIDIA NVIDIA Omniverse Launcher
MediumCVE-2025-48073: CWE-476: NULL Pointer Dereference in AcademySoftwareFoundation openexr
MediumCVE-2025-48072: CWE-125: Out-of-bounds Read in AcademySoftwareFoundation openexr
MediumCVE-2025-48071: CWE-122: Heap-based Buffer Overflow in AcademySoftwareFoundation openexr
HighCVE-2025-45768: n/a
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.