Security readout for executives and security teams
Plain-English summary
WP-Polls versions 2.76.0 and earlier can mishandle voting state under concurrent activity, allowing an authenticated subscriber-level user to affect poll integrity. The business impact is limited to data integrity, but public-facing WordPress sites using polls should verify exposure because abuse could distort results or trust in published poll data.
Executive priority
Treat as a routine but real integrity issue. Prioritize public WordPress sites where polls influence reputation, customer engagement, contests, or decision-making, especially if public user registration is enabled.
Technical view
CVE-2022-40130 is a CWE-362 race condition in the WP-Polls WordPress plugin through 2.76.0. The CVSS 3.1 score is 4.3: network exploitable, low complexity, subscriber-or-higher privileges required, no user interaction, unchanged scope, low integrity impact only.
Likely exposure
Exposure is limited to WordPress installations running WP-Polls 2.76.0 or earlier where untrusted users can authenticate as subscribers or above. Sites without the plugin, with newer unaffected versions, or without low-trust authenticated accounts are less exposed.
Exploitation context
The provided sources do not state active exploitation, and the supplied KEV status is false. Abuse requires authenticated access at subscriber level or higher, so risk depends heavily on whether the WordPress site allows public registration or broad low-privilege accounts.
Researcher notes
Public details in the bundle identify the weakness class, affected version range, privilege requirement, and CVSS vector, but not a detailed root cause, exploit evidence, or confirmed fixed version. Avoid assuming broader WordPress impact beyond WP-Polls.
Mitigation direction
- Inventory WordPress sites for WP-Polls installations and record plugin versions.
- If version is 2.76.0 or earlier, review vendor and Patchstack guidance before upgrading or replacing.
- Limit public subscriber registration where it is not operationally required.
- Review poll permissions and remove unnecessary access for low-trust users.
- Monitor poll data for unusual voting patterns or integrity anomalies.
Validation and detection
- Confirm whether WP-Polls is installed on each WordPress property.
- Verify installed version against the affected range: 2.76.0 or earlier.
- Check whether public registration or broad subscriber access is enabled.
- Review plugin changelog or vendor advisory for remediation status.
- Document affected sites and remediation decisions for vulnerability tracking.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-40130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.