BaseIncomplete

CWE-837Improper Enforcement of a Single, Unique Action

Category: other

Description

The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction. In various applications, a user is only expected to perform a certain action once, such as voting, requesting a refund, or making a purchase. When this restriction is not enforced, sometimes this can have security implications. For example, in a voting application, an attacker could attempt to "stuff the ballot box" by voting multiple times. If these votes are counted separately, then the attacker could directly affect who wins the vote. This could have significant business impact depending on the purpose of the product.

Common consequences· 1

  • Other — Varies by Context
    An attacker might be able to gain advantage over other users by performing the action multiple times, or affect the correctness of the product.

References

  1. https://cwe.mitre.org/data/definitions/837.html

(incoming)1

TypeTargetConfidenceTier
VulnerabilityCVE-2026-42609cve-2026-426090%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Control of Interaction Frequency
CWE
Improper Restriction of Excessive Authentication Attempts
CWE
Improper Authorization
CWE
Use of Multiple Resources with Duplicate Identifier
CWE
Improper Access Control
CWE
Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.