LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46611: WordPress YOP Poll plugin <= 6.5.28 - Vote Manipulation Due to Broken Captcha Control Vulnerability

Authentication Bypass by Primary Weakness vulnerability in yourownprogrammer YOP Poll allows Authentication Bypass.This issue affects YOP Poll: from n/a through 6.5.28.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability lets an unauthenticated visitor manipulate votes in the WordPress YOP Poll plugin by bypassing broken CAPTCHA control. The known impact is poll integrity, not data theft or site takeover. It matters most where poll results influence decisions, public credibility, contests, or user trust.

Executive priority

Handle during normal vulnerability remediation unless polls affect revenue, legal commitments, public reputation, contests, or customer-facing decisions. Escalate if high-value polls are public and unauthenticated voting is enabled.

Technical view

CVE-2023-46611 affects YOP Poll through 6.5.28. The source describes an authentication bypass by primary weakness tied to broken CAPTCHA control, enabling vote manipulation. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, with low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites running the YOP Poll plugin at version 6.5.28 or earlier. Public polls are the most relevant attack surface. The provided data does not identify affected CPEs or confirm whether non-public poll configurations are exposed.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Because CVSS indicates no authentication or user interaction is required, exposed public poll endpoints could be abused if a vulnerable plugin version is installed.

Researcher notes

Evidence is narrow but consistent: affected product, version range, weakness type, and CVSS are provided. The bundle does not include exploit details, a named fixed version, proof-of-concept status, or active exploitation confirmation.

Mitigation direction

  • Inventory WordPress sites using the YOP Poll plugin.
  • Check whether installed versions are 6.5.28 or earlier.
  • Consult vendor or Patchstack guidance for fixed-version availability.
  • Update the plugin if a supported fixed release is available.
  • Disable or remove YOP Poll where business use is not required.
  • Treat important poll results as untrusted until reviewed.

Validation and detection

  • Confirm YOP Poll is installed and record its exact version.
  • Review public pages for active polls using the plugin.
  • Check whether CAPTCHA-based vote controls are enabled or relied upon.
  • Review poll logs or results for unusual vote spikes.
  • Verify remediation by confirming the plugin is no longer at an affected version.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-305: 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 lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-46611 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-46611Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
yourownprogrammerYOP Pollyop-poll, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-305 · source CWE mapping

Authentication Bypass by Primary Weakness

Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.