Application security
PHP Application Security Check
PHP applications can be affected by vulnerabilities in the runtime, application code, dependencies and deployment configuration. Bravewall helps establish what applies to your environment, what needs attention and how agreed fixes can be verified.
Discuss a PHP security check
Why this matters
A vulnerability headline is a starting point, not an exposure assessment.
A public advisory can establish that a flaw exists and identify affected conditions. It cannot tell you whether a particular application runs an affected version, exposes the vulnerable component or has signs of compromise. Those questions require environment-specific evidence.
- Identify the PHP runtime and relevant application components
- Check affected-version and fix applicability against authoritative advisories
- Assess reachable exposure and relevant configuration
- Separate vulnerability assessment from investigation of suspected compromise
Global facts and updates
PHP2Shell: what the published advisories establish.
On 21 October 2026, the PHP project announced security releases for CVE-2026-109618 and CVE-2026-109619 and described both as critical remote-code-execution vulnerabilities. CISA added both to its Known Exploited Vulnerabilities catalogue on 26 October. The PHP project also published a separate informational notice on 23 October about a specific session-upload-progress configuration and said a full advisory for CVE-2026-115560 would follow with a later release. These dated global facts do not establish whether a particular application is affected or compromised. Sources last checked 10 November 2026; check current PHP and package-provider advisories before making a decision.
- Upstream fixed releases were PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; distributions and vendors may backport fixes
- A CVE listing is a threat signal, not an assessment of an individual application
- Confirm the actual runtime, deployment mode, vendor package and current fix status
Who may be affected
Start by confirming where PHP runs.
This check is for organisations of any size that operate a PHP application and need a scoped view of its security posture. PHP may be part of a customer-built application, a content management system, an API or another web service. A technology inventory and version details help establish whether the issue applies.
- Organisations operating PHP applications or services
- Teams that rely on a developer, host or managed service provider to confirm runtime details
- Owners who need validated findings and a prioritised remediation plan
PHP assessment questions
Look beyond the version number.
A useful review connects the PHP package to the application and the environment actually serving requests. These checks help distinguish a version that needs attention from a confirmed, reachable condition and from a separate incident concern.
- Runtime: identify the PHP handler and exact upstream or vendor package on every serving environment
- Application: review relevant code, dependencies and configuration against the applicable advisory
- Exposure: establish which vulnerable paths are present and reachable, and what controls limit impact
- Evidence: record provider statements, package notices, hosts checked, dates and remaining uncertainty
What the client receives
Leave with findings your team can act on.
The assessment is shaped around the application and agreed in the client conversation and SOW. Depending on that agreement, the work can produce a clear record of what was reviewed, what the evidence supports and what decisions remain.
- Validated findings with supporting evidence and affected components
- Priorities and remediation recommendations tied to the agreed application context
- A record of assumptions, exclusions and unresolved questions
- Agreed validation or retest results, where included in the SOW
Understand your risk
Risk depends on evidence from your application and environment.
Assessment considers the affected component and version, whether vulnerable functionality is present and reachable, relevant configuration, compensating controls and available indicators. A scan alone may not establish each of these. If compromise is suspected, that requires a separate investigation path and should not be treated as part of a routine vulnerability check.
- Potentially affected: version or component details need confirmation
- Exposure requiring action: applicable vulnerable conditions are present and reachable
- Suspected compromise: indicators or unexplained activity need incident investigation
How the check works
Move from scope to verified next steps.
The assessment is authorised in writing and scoped with the customer before testing. Remediation and any additional work are separately agreed.
- 01ScopeAgree the application, environment, access and written authorisation.
- 02AssessReview relevant versions and dependencies, perform targeted code analysis and validate findings.
- 03PrioritiseDocument severity, evidence, business context and remediation recommendations.
- 04FixThe application development team handles agreed remediation under a separately scoped work estimate.
- 05RetestBravewall verifies agreed fixes and records remaining findings within the agreed retest scope.
Before you enquire
Prepare for an initial conversation.
A first discussion can establish the application context and the questions you need answered. Scope, access, authorisation and any statement of work are handled through the client conversation. Do not submit credentials, logs or incident evidence through the general website contact form.
- Application type and business context
- PHP runtime or provider details, if known
- The concern or decision you want to address
Common questions
What the PHP security check can and cannot tell you.
The answers below explain what an application security review can establish and what belongs in the client conversation and statement of work.
- Does using PHP mean my application is vulnerable? No. The runtime and deployment evidence must be checked against the relevant vendor advisory.
- Does a vulnerability assessment prove there was no breach? No. Suspected compromise requires a separate incident investigation.
- Do you fix the code? Assessment findings and any remediation, validation or retesting arrangements are discussed with the client and recorded in the statement of work.
- Do I need to prepare access? Access and written authorisation requirements are agreed with the client before testing begins.
Related reading
Prepare the evidence behind an application security review.
A practical guide to documenting application security posture, remediation evidence and open questions.
PHP2Shell explained: what PHP application owners need to know
What PHP project advisories and CISA’s exploitation catalogue say about PHP2Shell, how to check whether a deployment may be affected, and what to do next.
Read article 02How to check whether your PHP application may be affected
A practical evidence checklist for confirming the PHP runtime, deployment mode, package and security update used by a production application.
Read article 03PHP security updates: patch, validate and plan the upgrade
Follow PHP vendor guidance, apply security updates, verify every production instance and plan a supported branch upgrade; retain clear ownership and evidence.
Read article 04A PHP vulnerability is not proof of a breach: when to investigate
Understand the difference between a vulnerable PHP deployment and a suspected compromise, what evidence matters and when to use an incident-response process.
Read articleNext step
Discuss a PHP security check
Bring the requirement, constraint or unresolved decision. We will help structure what comes next.
