This October, a pair of critical vulnerabilities in PHP became known as PHP2Shell. They allow an attacker to run commands on a server that uses an affected version of PHP, and they are being exploited in the wild. Security teams everywhere are asking their vendors a simple question: is PHP anywhere in your stack?
For OMEGA Revenue Engine, the answer is no.
The statement
PHP is nowhere on the books of OMEGA Revenue Engine. It is not in our websites, our applications, our dialers or our phone switches, and it never will be. That is by design. PHP was never part of the OMEGA Revenue Engine architecture.
We want to be precise about scope. This statement is about OMEGA Revenue Engine: its platform, its websites and the voice systems it runs. It is not a statement about any other company's systems.
Why PHP matters so much
PHP runs a very large share of the web. Content management systems, e-commerce platforms, plugins and, in the telephony world, the web screens of many dialers and phone switches are written in it. That popularity is exactly why a vulnerability in PHP is so serious: the same weakness exists in a vast number of places at once, and attackers can scan the internet for every one of them.
When a business depends on software it did not write, it inherits that software's weaknesses. Every plugin, every third-party module and every bundled web screen is a door someone else built.
Why we code from scratch
OMEGA Revenue Engine codes everything from scratch. That includes the platform, the websites, the voice gateway, the switching and the connectors. It is slower than assembling a product from popular parts. We think it is the only responsible way to build a system that businesses trust with their customers' conversations.
There are three reasons.
We know every line. When a vulnerability is announced in a popular framework, the first question for most companies is whether they are affected, and answering it can take days. When you write your own code, you know what is in it.
We choose the attack surface. Every component a system includes is something that could be attacked. Building from scratch means including only what the work needs, and nothing that came along for the ride.
We control the fix. If something does need changing, we change it. We do not wait for a third party's release, or for a plugin author who may have moved on.
Design, not a one-time check
It would be easy to write "we checked our servers and found no PHP". We deliberately do not put it that way. A check is a moment in time. Design is a decision that holds. PHP is absent from OMEGA Revenue Engine because the architecture never included it, and the way we build keeps it that way.
What to ask your vendors
PHP2Shell is a useful prompt to ask every vendor three questions.
- Is PHP, or any other widely exploited framework, anywhere in your product, including admin screens, dialers and phone systems?
- How much of your product did you write yourselves, and how much is assembled from third-party components?
- When the next critical vulnerability is announced, how quickly can you tell me whether I am affected?
The answers will tell you a great deal about how a vendor thinks about your risk.
How it fits
Coding from scratch is part of what sovereign means to us. A business that owns its model, its server and its network should not be exposed through a framework nobody on the team chose. The same discipline runs through every pillar of OMEGA.
Schedule a Call if your security team would like to go through the architecture with us.
Questions people ask
What is PHP2Shell? The name given to a pair of critical PHP vulnerabilities disclosed in October 2026 that can let an attacker run commands on an affected server. They are being exploited in the wild.
Is OMEGA Revenue Engine affected? No. PHP is not part of the OMEGA Revenue Engine architecture: not in its websites, applications, dialers or phone switches. That is by design.
Does this statement cover other companies' systems? No. It covers OMEGA Revenue Engine only.
Why not just use popular frameworks and patch them? Because every third-party component is a door someone else built. Writing our own code means we know every line, choose the attack surface and control the fix.
Tell SARAH your biggest marketing or sales problem and she will tell you how Omega can help.