Preconditions and environment

• Magento version : 2.4.3-p1
• Open vendor/magento/module-sales-graph-ql/Model/OrderItem/DataProvider.php and goto line 150. Here a implementation specific method (getStatus) is called on an interface. This method does not exists in the interface.

Steps to reproduce

• Open vendor/magento/module-sales-graph-ql/Model/OrderItem/DataProvider.php
• Go to function fetch()::112
• At line 126 $orderItem represents an OrderItemInterface
• At line 150 $orderItem->getStatus() is called but this method doesn't exists in the service contract. It is a method specific to Magento\Sales\Model\Order\Item which implements the service contract.

Expected result

If a status should be provided, it should either be done using extension attributes or a resolver class.

Actual result

Function fetch()::112 will use an implementation specific method at line 140 : $orderItem->getStatus() when this method does not exists in the service contract.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.