IonCube Decoder for PHP 7.3
Online

PHP 7.3 at a glance

Released

December 2018

End of life

December 2021

Zend engine

Zend Engine 3.3

IonCube encoders that target it

IonCube 11 and 12 are the primary targets for PHP 7.3 files. IonCube 13+ can also compile for 7.3.

What PHP 7.3 introduced

Decoders for PHP 7.3 need to reconstruct opcodes for these language features specifically:

• Flexible heredoc and nowdoc syntax (closing marker indentation)
• List reference assignments ([&$a, &$b] = ...)
• is_countable() built-in
• array_key_first() and array_key_last()
• Trailing commas in function calls
• JSON_THROW_ON_ERROR flag

Why PHP 7.3 decoding still matters

• A large portion of WordPress commercial plugins shipped encoded against PHP 7.3 between 2019 and 2021.
• Magento 2 extensions during the same era commonly targeted PHP 7.3 + IonCube 12.
• Many hosts with long upgrade cycles still serve 7.3 — particularly in regulated industries.

Gotchas specific to decoding PHP 7.3

• Heredoc indentation rules changed in 7.3 — decoded strings may not roundtrip byte-for-byte if the original used the older strict format.
• PHP 7.3 removed image2wbmp() and other deprecated functions; decoded code that called them needs polyfills on modern PHP.
• JSON_THROW_ON_ERROR is a new opcode in 7.3's json_decode path; decoders built for 7.2 can miscompile it.

File signature

An IonCube-encoded file targeting PHP 7.3 typically begins with a header that looks like this:

<?php //004fb2a3\n<?php //PHP73+\nHR+cPkX...

The first line encodes a header hash, the second encodes the PHP target, and the remainder is the encrypted bytecode payload. Our free in-browser version detector reads these bytes to identify the exact encoder and PHP target for your file.