Activity Reactions For BuddypressWordPress extension · Areteit
CVE-2022-45074
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 Paramveer Singh for Arete IT Private Limited Activity Reactions For Buddypress plugin <= 1.0.22 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 Activity Reactions For Buddypress WordPress plugin versions 1.0.22 and earlier. The plugin lacks proper anti-CSRF token validation on state-changing actions, allowing attackers to trick authenticated users into performing unintended operations such as modifying activity reactions without their consent.
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
Activity Reactions For BuddypressWordPress extension
<= 1.0.22CVSS 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.
-
Verify plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check for the 'areteit-activity-reactions-for-buddypress' folder in wp-content/plugins/Affected if The plugin 'Areteit Activity Reactions For Buddypress' appears in the installed plugins list
-
Identify installed versionIn WordPress admin > Plugins, find the plugin and read the version number displayed beneath the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if The version displayed is 1.0.22 or lower
-
Compare against affected rangeCompare the identified version number to the affected range: versions 1.0.22 and earlierAffected if The installed version is 1.0.22 or any version lower (e.g., 1.0.21, 1.0.20, etc.)
-
Inspect plugin for state-changing actions without nonce verificationExamine the plugin source code, specifically AJAX handlers (wp_ajax_* hooks) and form processing functions. Look for calls to wp_verify_nonce(), check_ajax_referer(), or wp_nonce_field() before processing state-changing operations like modifying activity reactionsAffected if State-changing actions (adding/removing reactions, updating reaction counts) process requests without verifying a nonce token
You are affected if the Areteit Activity Reactions For Buddypress plugin is installed at version 1.0.22 or lower, and the plugin code does not validate anti-CSRF tokens on functions that modify activity reactions.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints that perform state-changing operations, and verify the nonce on the server side before processing any request.
Fix this in Activity Reactions For Buddypress
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45074 — 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-45074 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