BadgeosWordPress extension
CVE-2022-41987
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in LearningTimes BadgeOS plugin <= 3.7.1.6 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the LearningTimes BadgeOS WordPress plugin versions 3.7.1.6 and below allows attackers to trick authenticated users into performing unintended administrative actions by forging malicious requests.
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
BadgeosWordPress extension
<= 3.7.1.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate BadgeOS plugin installationCheck if the directory wp-content/plugins/badgeos/ exists on the WordPress server file system.Affected if The badgeos directory does not exist, meaning the plugin is not installed.
-
Identify installed BadgeOS versionOpen the main BadgeOS plugin file (such as badgeos.php or index.php in the badgeos plugin directory) and locate the version number in the plugin header comment at the top of the file.Affected if The version number displayed is 3.7.1.6 or lower.
-
Confirm plugin is activeIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and verify whether BadgeOS is currently activated.Affected if BadgeOS is activated and the version is 3.7.1.6 or lower.
-
Verify admin capability exposureAttempt to access a BadgeOS administrative function that modifies settings, achievements, or ranks to confirm the plugin handles state-changing requests.Affected if The plugin accepts and processes administrative actions without requiring explicit anti-CSRF token verification, as the vulnerability allows forged requests to succeed.
If BadgeOS version 3.7.1.6 or lower is installed and active, the environment is affected by this CSRF vulnerability.
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.
dbcve · scopedImplement anti-CSRF tokens (nonces) on all state-changing operations and validate request origin via referer headers or SameSite cookie attributes.
BadgeOS version 3.7.1.7 or later
- Check WordPress admin dashboard for BadgeOS plugin updates
- Update BadgeOS to the latest available version
- Verify the update was successful
- Check BadgeOS changelog or security advisories for version 3.7.1.7 or higher which should contain the CSRF fix
- If no update available, consider temporarily disabling the plugin until a patched version is released
- Review WordPress security best practices for CSRF protection
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Badgeos
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41987 — 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-2022-41987 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