All in One Social Lite <= 1.0 - Server-Side Request Forgery
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- All in One Social Lite
- Affected Version
<= 1.0- CVSS
- 8.3High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Server-Side Request Forgery (SSRF) vulnerability in the All in One Social Lite WordPress plugin, affecting versions <= 1.0. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2014, reported by Anant Shrivastava (anantshri).
Vulnerability Overview
The All in One Social Lite plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.0 via the 'ajax-cube3x-stumpleupon-count.php' file. This makes it possible for unauthenticated attackers to gain otherwise restricted information from the vulnerable service and potentially execute malicious code remotely.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in All in One Social Lite <= 1.0 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for All in One Social Lite yet, so installs running <= 1.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to All in One Social Lite: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C