Radar sectionsDatabase
Check my site
WordPress plugin

WP-Recall <= 16.26.11 — Authenticated (Admin+) Stored Cross-Site Scripting

CVE-2024-9771Published · Updated

Action summary

Affected: ≤16.26.11Update to 16.26.12 or newer

All remediation steps
Severity
Medium4.4
CVSS
4.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:H Attack complexity
High
PR:H Privileges required
High
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-89 SQL Injection
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WP-Recall – Registration, Profile, Commerce & More wp-recall

  1. Affected≤ 16.26.11
  2. Patched in16.26.12

Update to 16.26.12 or newer.

You are affected if you run ≤ 16.26.11. Version 16.26.12 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP-Recall – Registration, Profile, Commerce & More.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 16.26.12, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP-Recall – Registration, Profile, Commerce & More to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Bob Matyas.

The WP-Recall plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 16.26.11 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP-Recall – Registration, Profile, Commerce & More

All 17
More vulnerabilities in WP-Recall – Registration, Profile, Commerce & More
SeverityVulnerabilityCVEPublished
Medium6.1Reflected Cross-Site Scripting
≤16.26.14No patch available
CVE-2025-52796
Medium5.3Missing Authorization
≤16.26.14No patch available
CVE-2025-49991
Medium4.3Cross-Site Request Forgery
≤16.26.14No patch available
CVE-2025-30981
High8.8Authenticated (Contributor+) Local File Inclusion
≤16.26.14No patch available
CVE-2025-47653
High7.5Unauthenticated SQL Injection
≤16.26.10Update to 16.26.12
CVE-2025-1323

Same weakness (SQL Injection)

All SQL Injection
Other SQL Injection vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 4.4

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?