On this page

CWE-436: Interpretation Conflict

Weakness Summary

Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

  • Canonical source: MITRE CWE-436
  • Published Atomicorp CVE observations: 1
  • Distinct affected products in those observations: 1
  • Active Atomicorp rules associated with this weakness: 2

Atomicorp Research Context

Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.

The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.

A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.

Selected Published CVE Observations

CVEVulnerabilityProductAtomicorp findingObserved rules
CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code ExecutionWordPressAttack Blocked by Atomicorp340156 , 344370

Associated Atomicorp WAF Rules

RuleStatusBehavior
340156Activedisruptive (deny)
344370Activedisruptive (deny)

MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims:

CAPEC-105 , CAPEC-273 , CAPEC-34