PHP2Shell, rated Critical

Running old PHP? A fix is out. We check your site and handle it.

The fixed PHP releases came out 10/21/26. Updating WordPress does not apply them. We find out where your site stands.

Or get a free quote.

run php2shell-check waiting on you
  1. intakeYour site and its PHP version
  2. checkIs the fixed PHP release in place?
  3. patchUpdate applied in a set time window
  4. proofWritten note: old version, new version, pages tested
  5. youYou confirm it works
How a check runs, step by step.
  • A person reads every request
  • Nothing changes until you say yes
  • The scope and price in writing before any work

The fix is out, so now is a good, easy time to get it done.

Does this apply to me?

I have a WordPress site

WordPress runs on PHP, so this applies to the server your site lives on. Updating WordPress itself does not apply the fix, and your host may already have done it. Send us your address and a person will tell you where you stand.

Someone built my site

Possibly. The free quote settles it either way.

I am not sure what I have

That is fine. Many sites use PHP without the owner ever hearing the word. WordPress does, and so do many site builders and custom sites. Not knowing is normal, and we will work it out with you.

I use Wix, Squarespace, Shopify or WordPress.com

The platform maintains the server, so you do not need us.

How it works

  1. 1

    You ask

    Send your web address.

  2. 2

    You agree

    We confirm scope and price in writing.

  3. 3

    We fix it

    We update the PHP and check your site.

  4. 4

    You get proof

    A written note of what we changed.

What it costs

One site

$99

Check, fix and proof note

What is included
  • The $99 always buys the check.
  • On PHP 8.2 to 8.5 with a standard setup, the fix is included. Anything more gets a fixed quote first, and you are never charged more than $99 without agreeing.
  • If the check shows you need more and you decline the quote, the $99 stays as the price of the check.
  • Not included: older PHP, a move to a new branch, repairs to plugins or custom code.

What you accept at checkout

I ask DX Dev to start now and agree the $99 fee is non-refundable once the check is delivered (Terms).

Up to three sites

$239

Check, fix and proof note

What is included
  • The $239 always buys the check of up to three sites.
  • Each site on PHP 8.2 to 8.5 with a standard setup gets the fix. Anything more gets a fixed quote first, and you are never charged more than $239 without agreeing.
  • Not included: older PHP, a move to a new branch, repairs to plugins or custom code.

What you accept at checkout

I ask DX Dev to start now and agree the $239 fee is non-refundable once the check is delivered (Terms).

Per site

$199

Migration review

Only needed if your site is on a version that cannot get the fix. The free quote tells you if that is you.

What is included
  • A written plan: options, risks and a rough timeline.
  • A fixed quote for the move, credited with the fee if you go ahead with us within 30 days.
  • Not included: doing the move itself.

What you accept at checkout

I ask DX Dev to start now and agree the $199 fee is non-refundable once the plan is delivered (Terms).

Never more than the price shown without your yes.

The free quote costs nothing. A person replies with a fixed price.

Check us out before you pay

  • A person reads every request.
  • We confirm the scope in writing before any work.
  • Never more than the price shown without your yes.

DX DEV INC, a Florida corporation. Our terms are published, and every job ends with a written proof note.

Why the free quote is free: it is how we earn the paid work. If you do not need us, we say so.

Ask us anything before you pay Answers, what each side gets and risks, and the full contract

These are the questions a careful buyer asks, answered from our posted terms. If something is not answered, ask it in the request form before you pay.

Show me the actual contract

Who does the work?

DX DEV INC does the work. It is AI-assisted development, with a person reviewing and signing off the written scope and the results before anything is sent to you.

Will I see the scope and the price in writing before I am billed?

For quoted work, yes: you pay only after you agree to the written scope and price, and the price in your written confirmation is the price you pay. A package is paid at checkout, but work starts only after we confirm the scope with you in writing.

If your change breaks something, who fixes it, and does it cost extra?

We do, at no charge. If within 10 business days of our note our change breaks a function listed in the written scope, tell us and we restore the previous PHP version at no charge within 1 business day. We treat a failure of a listed function inside that window as caused by our change unless we show you in writing that it was not. What is separate work: if the new PHP exposes a problem in old plugins or custom code, we tell you what breaks and restore the previous version if you want it, and repairs are quoted as separate work.

What does a rollback cover, and what are its limits?

A rollback puts your previous PHP version back, at no charge. It applies when a listed function breaks because of our change within 10 business days of our note. Its limits: it restores the PHP version, not your data or files, which is why you confirm a current backup you can restore before we start. Only the pages and functions listed in the written scope are tested and covered. Going back to the old version also brings the old flaw back, so it is a way out and not a fix.

Do you test on a staging copy first and deploy only when I authorize it?

We do not promise a staging copy. What we do commit to is this: work starts only after we confirm the scope with you in writing, you confirm your backup, and you give us the access it needs. After the change we check that the site responds and that the pages and functions listed in the written scope still work, then send a short written note of what we found and changed.

How much access do you need, and what happens to it afterwards?

The least access the job needs, and we name the method in the written scope. Send access details only that way, never through the request form. We use access only for the agreed work on the named site, keep what we see confidential, and delete the details when the work ends. We tell you in writing when we have deleted them. You should also remove our access and change any password you shared.

Who owns what you deliver?

Your site, your files and your data stay yours, and we touch them only for the agreed work. What you receive is the changed setup on your site and a short written note of the old and new version and the checks we ran.

Which law applies, and what if we disagree?

DX DEV INC is a Florida corporation and the laws of the State of Florida apply. Send any question or problem through the request form. The terms shown when you pay (packages) or accept the written scope (quotes) apply to that order, and we will not change them for that order without your written agreement.

Who am I dealing with?

DX DEV INC, a Florida corporation, trading as DXDEV. Our terms are published on this page, and every job ends with a written proof note of what we found and changed. Questions go through the request form.

What each side gets, and what each side risks

You get

  • A person reads your request. For quoted work you see the scope and price in writing before you pay. A package is paid at checkout, and work starts only after we confirm the scope in writing.
  • Your site's PHP checked and moved to a fixed version, then a written note of old and new version and the checks run.
  • A rollback if our change breaks a function listed in the written scope.

You risk

  • A package is binding once you pay. Quoted work binds once you agree to the written price.
  • The fee is non-refundable once the check is delivered.
  • Older plugins or custom code can break on a newer PHP. We tell you what breaks. Repairs are separate work.
  • Our liability is limited to the fee you paid, with the exceptions listed in the full terms. Backups are your job.

We get

  • A fixed fee for a defined job, and your confirmation that you may authorize the work.
  • A backup you can restore, and the least access the job needs.
  • The right to decline a job if we cannot do it safely.

We risk

  • Doing the work before you check it, then fixing what our own checks missed.
  • Holding access to your hosting while we work, which we limit, keep confidential and delete.

If your host does not let us make the change, we tell you plainly and help you find the next step.

Check us with your own AI

Show prompt textHide prompt text

A company called DX DEV INC, a Florida corporation, offers to check and fix the PHP on my website for $99. The $99 always buys the check. If my site is on a supported PHP version with a standard setup, the fix is included. Anything more gets a fixed quote first, and I am never charged more than $99 without agreeing. If the check shows I need more and I decline the quote, the $99 stays as the price of the check. They say a person reads every request, gives a written scope before any work, publishes its terms, and ends the job with a written proof note of what it changed. Is that a reasonable, safe way to get my site fixed? What should I check before hiring a company like that, and what questions should I ask? More info: dxdev.com/php2shell

Get your free quote

A person replies within two business days with a fixed price. Nothing is charged until you agree. No reply within two business days? Send the form again and we will follow up.

Add more detail
Scope your request (optional, it sharpens the estimate)

Your estimate

Choose your PHP version to see an estimate.

A fixed package shows its exact price. Any other estimate is a non-binding range. Sending this form is the free quote: a person replies with advice and a fixed price.

No passwords or keys, please. Sent through Web3Forms.

If you want to prepare

None of this is required.

Find your logins and accounts Domain, host and site admin. Not knowing is normal.

1Find your domain

Your domain is your web address, like example.com. It is registered with a company called a registrar, and that account is separate from your hosting.

Look in your email for renewal notices and receipts. Search for "domain" or "renewal". A free lookup tool that takes your site address can also show the registrar.

Show prompt textHide prompt text

I own a website but I am not technical. My site address is [your site address]. Explain in simple steps how to find out which company my domain name is registered with. Show me how to use a free WHOIS or domain lookup tool, what to look for in the result, and where in my email to search for renewal notices. Use plain words and short steps. More info: dxdev.com/php2shell

2Find your host

Your host is the company whose server runs your site. It may be a different company from your registrar.

Check old invoices and card statements for a monthly or yearly hosting charge. Look in your email for "cPanel", "hosting" or "server". If a developer built the site, ask them who the hosting account belongs to.

Show prompt textHide prompt text

I own a website at [your site address] and I am not technical. Explain in simple steps how to find out which company hosts it. Include how to use a free lookup tool that shows the hosting company from a site address, what to search for in my email and card statements, and what to ask a former developer. Use plain words and short steps. More info: dxdev.com/php2shell

3Check you can log in to three places

You need your hosting panel, your site admin (for example WordPress at yoursite.com/wp-admin) and your domain registrar.

You do not have to hand these to anyone yet. You only need to know they work. If one does not, start the password reset now, because recovery can take a day or two when the account is under an old email address.

Show prompt textHide prompt text

I own a website and need to confirm I can log in to three places: my hosting control panel, my site admin (WordPress), and my domain registrar. My host is [host name], my registrar is [registrar name]. For each one, tell me in simple steps where the login page is, how to reset a forgotten password, and what to do if the account is under a former developer's email. Use plain words. More info: dxdev.com/php2shell

Cannot get back in? That is not a dead end.

Get back in, through your own host and registrar. Account recovery goes through the company that holds the account, using proof that you own the domain and the business. We walk you through it step by step. We never ask for your password.

Start fresh on a modern setup. If recovery is not possible, we can rebuild your site from your own public content, with your written authorization. We confirm the site is yours, or that you are authorized to manage it, before we start.

A checklist for anyone who works on your site

Checklist for any contractor who updates the PHP on your website

Hand this to whoever does the work, us or anyone else. It keeps the job safe, and it keeps you in control. Tick each line before you say yes. It is useful even if you hire someone else.

Before starting

  • You have the contractor's scope and price in writing, and you agreed to it.
  • The scope names the site address, the PHP version it runs now, and the version it should end on.
  • The scope lists the pages and functions that must still work afterwards (home page, login, any form or checkout page).
  • You know who your host is, and whether the host has to allow the change.
  • You named one person who can approve the work and answer questions the same day.

Access they will need (the least that does the job)

  • Only the access the job needs, for only the site named in the scope. Not every account you own.
  • Agreed in writing: which method (hosting panel, a temporary user, SSH if needed) and for how long.
  • Shared only the way the contractor asks, never through a public form, a chat group or a shared document.
  • A separate login for the contractor where the host allows it, so you can switch it off later.

A backup comes first

  • A current backup of the site files and the database exists before anything changes.
  • You know where it is and you (or the host) can restore it. A backup nobody can restore is not a backup.
  • If the contractor cannot see a workable way back, they should say so and stop.

During the work

  • The contractor tells you before changing anything that is outside the scope.
  • Anything extra gets a written price first. You can say no.
  • If the host blocks the change, the contractor says so plainly and does not pretend the site is safe.
  • You can reach the contractor if the site misbehaves while they work.

After the work, confirm

  • The new PHP version is the one actually serving your site, and the old version is named in writing.
  • Your home page, your login, and every form or checkout page in the scope still work. Try them yourself.
  • You received a short written note: what was found, what changed, which checks ran.
  • You know how to go back to the old version, and who does it, if something listed breaks.
  • The contractor's access is removed and any password you shared is changed.

Never share in a public chat or email

  • Passwords, or a login together with its password in one message.
  • Full credentials for your host, your domain registrar or your payment account.
  • Private keys, API keys, tokens or a database password.
  • Customer lists, card numbers or other personal data.
  • If a contractor asks for any of these in an open chat or an email, stop and ask for a safer method.

Sign-off

  • You tested the pages and functions in the scope.
  • You have the written note and a restorable backup.
  • Access is removed and shared passwords are changed.
  • You agree the job is finished, in writing, before the final payment on quoted work.

More info: dxdev.com/php2shell

Download as text

Other things we help with Security review, modernization advice

Security review

A plain-language write-up of what we can see about your site's security: software that is out of date, settings worth changing, and what to fix first. It reports findings. It is not a promise that a site is secure.

Modernization suggestions

Advice on moving off outdated technology, such as old PHP or an unsupported theme or plugin: what to change, in what order, and what it involves. You get the suggestions in writing. Any build work is quoted separately.

Both are quoted after a short conversation. A person replies, and nothing is charged until you agree in writing.

For technical readers

The technical details

The flaw and the fixed versions
  • 2 critical flaws, CVE-2026-109618 and CVE-2026-109619
  • Critical rated on both NVD records, CVSS 4.0 score 9.2 and CVSS 3.1 score 9.8
  • 5.4+ nearly every PHP version back to 5.4 is affected

On 10/21/26 the PHP project released security updates for two flaws, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed PHP2Shell. Both let someone who is not logged in run code on a web server. Rated Critical: CVSS 4.0 score 9.2 from the PHP project, and CVSS 3.1 score 9.8 from NVD, both listed on the NVD record. They sit in PHP's engine, not in any one website, so even a site with clean code is exposed on a vulnerable version.

The fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Apache with mod_php carries the highest risk, where one request can trigger the attack before any of your site code runs. An attacker may also be able to read memory from the PHP process, which can hold passwords, tokens and keys from other requests.

Cloudflare said before the patch shipped that it was seeing early exploit attempts. As of 7:26 am on 10/21/26, one researcher who reproduced the first flaw reported no exploitation in the wild, and neither flaw was in CISA's Known Exploited Vulnerabilities catalog at that time. That is what the two outlets below report, not something we measured, and it can change fast.

Update to at least
PHP 8.58.5.12
PHP 8.48.4.27
PHP 8.38.3.36
PHP 8.28.2.35
PHP 8.1 and olderNo updates from PHP

PHP 8.2 reaches end of life on 12/31/26. A distribution package can carry the fix under an old looking version number, so the version string alone does not always tell the whole story. We check the package changelog for the CVE.

Who is at risk

  • Anyone running WordPress, Laravel, Drupal, Magento or any other PHP site.
  • Sites on a VPS or dedicated server where nobody has touched the PHP package recently.
  • Sites still on PHP 8.1 or older. The PHP project no longer updates those branches, so the real fix is a move to a supported version, or a backport from your hosting vendor.
  • Sites on PHP 8.2. It gets the fix, but reaches end of life on 12/31/26, so a newer branch is the better target.

Shared hosting caveat. On shared hosting, your provider controls the PHP runtime. Often the only thing anyone can do on your side is switch the PHP version in the host's control panel, or ask the host when its patched build lands. We can tell you which it is and do what your account allows. If your host has not shipped a fix and gives you no way to move, we will say so plainly instead of pretending the site is safe.

Sources: The Hacker News and Help Net Security, both 10/21/26. Primary records: NVD CVE-2026-109618, NVD CVE-2026-109619, PHP 8.5.12 release notes. Also read: Wiz research write-up and Cloudflare's WAF note.

Check these facts with your own AI

Show prompt textHide prompt text

Please verify each claim below against official sources (for example NVD at nvd.nist.gov and php.net). Return a table with three columns: claim | Correct / Partly correct / Incorrect | official source to confirm it. Claims: 1) Two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were published on NVD on 10/21/26. 2) Both are rated Critical on their NVD records: CVSS 4.0 score 9.2 from the PHP project, and CVSS 3.1 score 9.8 from NVD. 3) The PHP project released security updates on 10/21/26: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. 4) PHP 8.1 and older no longer receive security fixes from the PHP project. 5) Updating WordPress alone does not fix this, because the flaw is in PHP itself, so the PHP version on the server has to change. After the table, tell me in plain words how urgent this is for a small business website. More info: dxdev.com/php2shell

Check your PHP version
  • WordPress: Tools, then Site Health, then the Info tab, then Server. PHP version is listed there.
  • cPanel hosting: open MultiPHP Manager. It shows the version for each domain.
  • Your own server: run php -v. The command line version can differ from the one your web server uses, so also check php-fpm -v or your Apache module.

A version number alone does not prove you are safe or exposed. Some hosts patch under the old number.

Show prompt textHide prompt text

I run a WordPress site on [host name]. Explain in simple steps how to find out which PHP version my site is running, both inside WordPress (Site Health) and in a typical hosting control panel. Then tell me which PHP versions are currently supported according to php.net and what it means if mine is older. Do not tell me to change anything yet. Use plain words. More info: dxdev.com/php2shell

How we check and what we change

We find the PHP version and server setup your site actually runs on, and whether it is exposed. We move the site to a fixed release on its current supported branch (8.2 to 8.5) and restart what needs restarting. We confirm the new version is the one serving requests and that your site still loads and works. Then we send a short written note of the old and new version and the checks we ran. If you are on an older branch that no longer gets updates, or need a move to a newer one, we quote it in writing first.

The full terms

Terms version 2026-10-24

Short and fair, with nothing hidden. Read it here, or copy it and ask your own AI whether it is fair to you.

Show prompt textHide prompt text

"Check this with your AI" copies this prompt followed by the full terms, exactly as written below: Here are the terms of a PHP fix service. Are they fair and reasonable for a customer? What would you watch out for? Paste it into ChatGPT or any assistant.

Two ways to buy

The estimate in the request form never charges anything and is never binding. Sending the request form is free and carries no obligation. Quoted work: you send your details, a person replies with advice and a fixed quote, and you pay only after you agree to it. The $99 check and patch is a package and works as described under Prices. Packages: you choose a fixed package, accept these terms and pay on Stripe Checkout.

The work

For the one site you name: we find the PHP version and server setup, save a copy of the PHP and web server settings we touch, move the site to a fixed release on its current supported branch (8.2 to 8.5), restart what needs restarting (this can briefly interrupt your site, so we agree a time with you first), check that the site responds afterwards and that the pages and functions we list in the written scope still work (we record each one before and after the change), and send a short written note.

We install a PHP build that carries the fix for PHP2Shell (CVE-2026-109618 and CVE-2026-109619): either the fixed release from the PHP project or your host's or distribution's patched package. Where your host controls PHP, we select the patched version your host offers. If none of them carries the fix, we say so in writing. The note names the build, the old version, how we confirmed the fix, and the checks we ran. The scope always lists your home page, your login, and any form or checkout page you name. You can add any function you name in writing before work starts. Unless the written scope says otherwise, the change is made on your live site. Anything not listed is not tested. One site per request unless we agree otherwise in writing.

Prices

The $99 always buys the check. Supported version and standard setup: patch included. Anything more gets a fixed quote, agreed first, and is never charged above $99 without agreement.

The $99 always buys the check and verification of your PHP and setup. The check is a written report of your PHP version, your setup and what it needs. If you are already on a supported version with a standard setup and no feature migration is needed, the patch is included in the $99 and nothing more is due. If you are on an older or unsupported version, or your setup needs extra work (a feature migration, compatibility changes, anything that adds time), we tell you first and give a fixed quote for the extra before doing any of it. You are never charged more than $99 without agreeing to that quote. A standard setup means one PHP site on one host, where the PHP version can be changed through the hosting panel, php-fpm or the package manager, with no custom-built PHP extensions and no code changes needed. We tell you in writing, after the check, which side you are on, with the reasons.

If you say no to a quote, you keep the check results and the written note. The price in your written confirmation is the price you pay. Extra sites or changed scope are quoted in writing before we start them. A written quote is valid for 7 days from the day we send it. You can also buy the migration review for older PHP.

Packages

Quick package, $99: Always covers the check and verification of your PHP and setup. The patch is included on PHP 8.2 to 8.5 with a standard setup. Anything more gets a fixed quote first. Covered by our posted terms.

Three-sites package, $239: The same for up to three sites on one hosting account. The fee terms under The fee apply to the $239 as they do to the $99.

Migration review, $199 per site: A written plan and fixed quote to move your site off outdated PHP. The fee counts toward the move if you go ahead within 30 days of the plan.

The three-sites package has one scope confirmation for all three sites, and the logic under Prices applies to each site: the check is always covered, the patch is included for each site on a supported version with a standard setup, and any site that needs extra work gets a fixed quote first. The migration review does not include doing the migration itself. After we deliver the migration review plan, the $199 fee is non-refundable. It is credited toward the migration if you go ahead with us within 30 days of the plan, and otherwise it stays paid for the plan you received. The quick and three-sites packages exclude older PHP, a move to a new branch, and repairs to plugins or custom code.

Not included

A malware scan or security audit. Repairs to plugins, themes, custom code, email, payments or other site features, unless the written scope says so. Fixing sites that already break on a newer PHP because of old plugins or custom code (we tell you what breaks and can quote that as separate work). Cleaning up a site that was already compromised. Anything your host controls and will not let us change. Hosting or bandwidth costs.

If our change breaks something

If, within 10 business days of our note, our change breaks a function listed in the written scope, tell us and we restore the previous PHP version and the saved settings at no charge within 1 business day of your report (within 1 business day of your host allowing it, if your host needs a ticket). The 10 business days count from the day after we email our note to the address you gave us. If you did not get the email, tell us and we resend it and the 10 days start again. We treat a failure of a listed function inside that window as caused by our change unless we show you in writing that it was not. If the new PHP exposes a problem in old plugins or custom code, we tell you what breaks, restore the previous version at no charge if you want it, and can quote repairs as separate work.

When work starts

We take a limited number of sites per week. If we are full, we say so and give you a date. We aim to reply within two business days. Business days are Monday to Friday, Eastern time, except US federal holidays. Work starts only after we confirm the scope with you in writing, you confirm the backup, and you give us the access it needs. Work starts when we email you that we have begun the check. We then aim to finish within two business days. These are targets, not guarantees. Hosts that need a ticket on their side can take longer, and we tell you.

Payment

Packages: you pay by card on Stripe Checkout and tick that you accept these terms first. Quoted work: the written quote states the price, when it is due and your cancellation rights, and these terms apply to anything the quote does not change. You agree to a quote by replying yes by email from the address you gave us, or by paying the link. We email you one Stripe payment link for the exact amount, after you agree to the written scope and price. For quoted work, nothing is charged automatically or before you use that link. Stripe emails your receipt. Each written quote names the version of these terms in force on the day we send it.

What you confirm

You tell us that you own the site or are authorized by its owner to have this work done, and that you have cleared it with your host where needed. You are responsible for any permission we need from your host or other third parties. Before we start, you confirm in writing that you have a current backup of your files and database that you can restore. If we cannot see a workable way back, we may decline the work.

Access

We ask for the least access the job needs and name the method in the written scope. Send access details only that way, never through the request form, a chat or the body of an email. We never ask for a password in plain email. We use access only for the agreed work on the named site, keep what we see confidential, and delete the details when the work ends. We tell you in writing when we have deleted your access details, and we delete them no later than 10 business days after our note. Access can expose your site data: we look only at what the change needs and do not copy it off your server. If we learn of unauthorized access to your details, we tell you within 3 business days. AI tools only see our own scripts and notes. Your access details, passwords, files and database contents never go into any AI service. You should also remove our access and change any password you shared.

The fee

The $99 fee pays for the PHP2Shell check itself, and you pay it whether or not you accept any follow-up quote. By paying you ask us to start the check right away. Once the check is delivered the fee is non-refundable. If you are a consumer in the EU or UK, you acknowledge you lose your 14-day cancellation right once the check is fully performed. If you cancel before then, you pay only for the work already done.

If the site looks already compromised

If during the check the site looks already compromised, we stop and tell you in writing what we saw. We do no further work. Cleanup is separate work, and we quote it only if you ask.

Limits on our liability

Our total liability for this service is limited to the fee you paid. This limit never reduces the free restore described in these terms. We are not liable for lost profit, lost data, downtime or other indirect loss. Neither limit applies to our fraud, gross negligence, willful misconduct, misuse of access details or breach of confidentiality, or where the law does not allow it. Patching removes a known flaw. We do not warrant against other vulnerabilities, a future attack, or damage that happened before we started. Backups are your responsibility.

Who we are, and changes

This service is provided by DX DEV INC, a Florida corporation. DXDEV is its brand. The laws of the State of Florida apply. Questions: through the request form. What we keep: your site address, your email, the written scope and our note, to run the job and answer questions, normally for no more than 90 days after the work ends. Stripe handles your card and we never see the card number. The request form is sent through Web3Forms. The terms shown when you pay (packages) or accept the written scope (quotes) apply to that order, and we will not change them for that order without your written agreement.

What you tick at checkout

Quick package: I ask DX Dev to start now and agree the $99 fee is non-refundable once the check is delivered (Terms).

Three-sites package: I ask DX Dev to start now and agree the $239 fee is non-refundable once the check is delivered (Terms).

Migration review: I ask DX Dev to start now and agree the $199 fee is non-refundable once the plan is delivered (Terms).

Questions and answers
Do I need to be technical to get my site patched for PHP2Shell?

No. The patch itself is the contractor's job. Your part is knowing three things: where your domain is registered, who hosts your site, and that you can log in to each. "Find your logins and accounts", under "If you want to prepare", shows how to find them. If you cannot find something, we can help work it out.

Does updating WordPress fix PHP2Shell?

No. The flaws sit in PHP itself, which runs on your server. WordPress, themes and plugins sit on top of it. The PHP version on the server has to change, which is usually done in the hosting panel or by the host.

How do I check which PHP version my site uses?

In WordPress, open Tools, then Site Health, then the Info tab, then Server, and look for the PHP version. Most hosting panels also show it. The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older get no update from the PHP project.

How do I find out who hosts my website?

Look for the hosting company in old invoices, your email (search for "hosting", "cPanel" or "renewal") or your card statements. A free lookup tool that takes your site address can also show the company behind it.

What if I lost the login to my domain or hosting?

This is common, especially when a former developer set things up. Registrars and hosts have a recovery process that proves you own the account. It can take a day or two, so start early. If you are stuck, write to us and we will help you work out who to contact.

Is the estimate in the request form binding?

No. The estimate never charges anything and is never binding. A package is binding once you accept the terms and pay. Quoted work binds once you agree to the written scope and price.

What does the $99 check, fix and proof note cover?

The $99 always buys the check. Supported version and standard setup: patch included. Anything more gets a fixed quote, agreed first, and is never charged above $99 without agreement. If the check shows you need more and you decline the quote, the $99 stays as the price of the check.

Do I pay before you look at my site?

Only for a package, and work still starts only after we confirm the scope with you in writing. Not ready to pay? Get a free quote: send your details in the request form and a person replies with advice and a fixed price. The free quote costs nothing.

Do I still pay the $99 if I do not take a follow-up quote?

Yes. The $99 pays for the check itself, and you pay it whether or not you accept any follow-up quote. By paying you ask us to start the check right away. Once the check is delivered the fee is non-refundable.

What should I never send to a contractor in a public chat or email?

Passwords, a login together with its password, full credentials for your host or domain registrar, private keys, API keys, tokens, database passwords, and customer or card data. Share access only the way the contractor asks, and ask for a safer method if they want any of these in an open chat or an email. The contractor checklist on this page lists it.

Is there a checklist I can give to any contractor?

Yes. "A checklist for anyone who works on your site", under "If you want to prepare", covers what to settle before starting, the least access they need, the backup that comes first, what to confirm after the work, what never to share, and the sign-off. You can copy it, print it or download it as text.

Do I need a backup?

Yes. Before we start, you confirm in writing that you have a current backup of your files and database that you can restore. If we cannot see a workable way back, we may decline the work.

Who is the other party and which law applies?

DX DEV INC, a Florida corporation. DXDEV is its brand. The laws of the State of Florida apply. Questions go through the request form.