Ask me
ask-me · theme
Known security vulnerabilities for Ask me. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
3 exploitable without logging in · latest Nov 21, 2022
Before you install
Maintenance unknown
- Not on wordpress.org (paid or third-party distribution); 4 known records.
Follow updates through the vendor's own channel; we cannot see from wordpress.org whether this component is current.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Not in the wordpress.org directory (paid or third-party distribution). We cannot verify its latest release or maintenance status here; fixed-version data comes from the record itself.
wordpress.org status checked on Oct 31, 2026
Vulnerabilities
- Medium 6.5
CVE-2022-1424login required→ 6.8.2
Ask Me < 6.8.2 - Multiple CSRF in AJAX Actions
- Medium 6.1
CVE-2022-1241unauthenticated · needs a click→ 6.8.2
Ask Me < 6.8.2 - Reflected Cross-Site Scripting
- Medium 4.7
CVE-2022-3750unauthenticated · needs a click→ 6.8.7
Ask Me < 6.8.7 - Post Deletion via CSRF
- Medium 4.3
CVE-2022-1251unauthenticated · needs a click→ 6.8.4
Ask Me < 6.8.4 - CSRF in Edit Profile
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).