Strategic Overview
- Status
- Unpatched
- Affected Plugin
- postTabs
- Affected Version
<= 2.10.6- CVSS
- 9.6Critical
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-1781
At a glance
CVE-2022-1781 is a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the postTabs WordPress plugin, affecting versions <= 2.10.6. It carries a CVSS score of 9.6 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2022, reported by Daniel Ruf.
Vulnerability Overview
The postTabs WordPress plugin through 2.10.6 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack, which also lead to Stored Cross-Site Scripting due to the lack of sanitisation and escaping
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in postTabs <= 2.10.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. No fixed build of this plugin is recorded for postTabs yet, so installs running <= 2.10.6 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 postTabs: 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