Wechat RewardWordPress extension · Wechat Reward Project
CVE-2021-24615
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Wechat Reward WordPress plugin through 1.7 does not sanitise or escape its QR settings, nor has any CSRF check in place, allowing attackers to make a logged in admin change the settings and perform Cross-Site Scripting attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Wechat Reward WordPress plugin through version 1.7 fails to sanitize or escape QR settings input and lacks CSRF protection, allowing authenticated attackers to inject malicious scripts via admin settings modifications, resulting in stored Cross-Site Scripting (XSS).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wechat RewardWordPress extension
<= 1.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Wechat Reward plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) or view installed plugins in WP Admin > Plugins. Look for a folder named 'wechat-reward' or 'wechat-reward-wordpress'.Affected if The plugin folder does not exist in the plugins directory.
-
Identify the installed plugin versionOpen the main plugin PHP file (typically wechat-reward.php or similar in wp-content/plugins/wechat-reward/) and locate the Version header in the plugin comment block. Alternatively, check the readme.txt file for the 'Stable tag' entry.Affected if The version is 1.7 or lower.
-
Confirm the plugin is activeIn WordPress Admin, go to Plugins > Installed Plugins and check if Wechat Reward shows as 'Active'. You can also query the wp_options table for the active_plugins option.Affected if The plugin shows as Active in WordPress.
-
Verify QR settings are accessibleIn WordPress Admin, navigate to the plugin settings page (usually under Settings > Wechat Reward or a dedicated Wechat Reward menu item). Attempt to access the QR settings fields where QR code configuration options are provided.Affected if The QR settings page loads and accepts input without requiring re-authentication.
The environment is affected if the Wechat Reward plugin is installed, active, and the installed version is 1.7 or lower, allowing an authenticated user with settings access to inject malicious scripts via QR settings fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a patched version immediately. If no patch exists, remove the plugin or implement manual sanitization of all QR settings fields and add nonce/CSRF validation to settings save actions.
Fix this in Wechat Reward
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-24615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data