Skip to main content
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-15377: CWE-352 Cross-Site Request Forgery (CSRF) in abage Sosh Share Buttons

0
Medium
VulnerabilityCVE-2025-15377cvecve-2025-15377cwe-352
Published: Wed Jan 14 2026 (01/14/2026, 05:28:06 UTC)
Source: CVE Database V5
Vendor/Project: abage
Product: Sosh Share Buttons

Description

The Sosh Share Buttons plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.0. This is due to missing nonce validation on the 'admin_page_content' function. This makes it possible for unauthenticated attackers to update the plugin's settings 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

AILast updated: 02/27/2026, 11:57:14 UTC

Technical Analysis

CVE-2025-15377 is a medium-severity security vulnerability classified as CWE-352 (Cross-Site Request Forgery) found in the abage Sosh Share Buttons plugin for WordPress. This vulnerability exists in all plugin versions up to and including 1.1.0 due to the absence of nonce validation in the 'admin_page_content' function. Nonces in WordPress are security tokens used to verify that requests are intentional and originate from legitimate users. Without nonce validation, attackers can craft malicious web requests that, when executed by an authenticated administrator (via clicking a link or visiting a malicious page), cause unauthorized changes to the plugin's settings. The attack vector is network-based (remote) with no privileges required, but it requires user interaction from an administrator. The vulnerability impacts the integrity of the plugin's configuration but does not compromise confidentiality or availability. The CVSS v3.1 score of 4.3 reflects the ease of exploitation (low complexity), no privileges required, but requiring user interaction and limited impact scope. No patches or official fixes are currently linked, and no known exploits have been observed in the wild. The vulnerability is significant because it allows attackers to manipulate plugin settings stealthily, potentially enabling further attacks or misconfigurations.

Potential Impact

The primary impact of CVE-2025-15377 is the unauthorized modification of the Sosh Share Buttons plugin settings by attackers without authentication, leveraging CSRF attacks against site administrators. This compromises the integrity of the plugin's configuration, which could lead to altered sharing behaviors, injection of malicious content, or enabling other attack vectors if the plugin settings control critical functionality. Although confidentiality and availability are not directly affected, the integrity breach can facilitate further exploitation or damage site reputation. Organizations relying on this plugin may face risks of unauthorized content manipulation or loss of control over social sharing features. Since exploitation requires administrator interaction, the attack surface is limited but still significant in environments with multiple administrators or where phishing attacks are feasible. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits post-disclosure.

Mitigation Recommendations

1. Immediate mitigation involves updating the Sosh Share Buttons plugin to a version that includes nonce validation once an official patch is released by the vendor. 2. Until a patch is available, administrators should avoid clicking on untrusted links or visiting suspicious websites while logged into WordPress admin. 3. Implement web application firewall (WAF) rules to detect and block suspicious POST requests targeting the plugin's admin endpoints. 4. Employ security plugins that add CSRF protections or monitor for unauthorized changes in plugin settings. 5. Educate administrators about phishing and social engineering risks to reduce the likelihood of interaction with malicious content. 6. Regularly audit plugin configurations and WordPress logs for unexpected changes. 7. Consider restricting administrative access by IP or using multi-factor authentication to reduce the risk of successful CSRF exploitation. 8. Monitor security advisories from the plugin vendor and WordPress community for updates or patches.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-30T20:12:22.347Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69672e018330e067168f4029

Added to database: 1/14/2026, 5:47:45 AM

Last enriched: 2/27/2026, 11:57:14 AM

Last updated: 3/25/2026, 1:20:18 AM

Views: 30

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 require Pro Console access. Upgrade inside Console → Billing.

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

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses