rewindex

ChangesDocuSignTrust page

DocuSign: Trust page changed

Trust / securityChanged (not classified) (rule)Changed www.docusign.com (opens in new tab)
Summary

DocuSign updated its PHP2Shell vulnerability alert to confirm that core services do not use PHP and are unaffected, and that its investigation found no indicators of compromise. A limited number of internal systems use PHP and are being remediated; the alert also links to PHP’s recommended mitigation measures.

Machine-written from the diff below (Sol; type: other). Check the diff before relying on it.

What changed

Struck in red is what DocuSign removed; blue is what they added. Muted text is unchanged context.

Changed#1
Before: …back here for any updates regarding the schedule. Alert: PHP2Shell Vulnerability ‹date› Docusign became aware of a critical vulnerability affecting…
After: …back here for any updates regarding the schedule. [UPDATED] Alert: PHP2Shell Vulnerability ‹date› [UPDATED: ‹date› ] On ‹date› , Docusign became aware of a critical vulnerability affecting…
Added#2
Before: …vulnerability affecting PHP, known as PHP2Shell. Details regarding nothing here are available in the PHP project’s security advisory:…
After: …vulnerability affecting PHP, known as PHP2Shell. Details regarding this vulnerability and PHP’s recommended mitigation measures are available in the PHP project’s security advisory:…
Added#3
Before: …PHP project’s security advisory: https://www.php.net/archive/2026.php# ‹date› -5 . nothing here On ‹date› Docusign became aware of a critical…
After: …PHP project’s security advisory: https://www.php.net/archive/2026.php# ‹date› -5 .   We can confirm that our core services do not use PHP and are not affected by this vulnerability. The Docusign security and engineering teams have completed a comprehensive investigation into PHP2Shell and found no indicators of compromise in our environment.  We have identified a limited number of internal Docusign systems that utilize PHP and we are actively remediating them. For developers, we are also updating our external integration documentation with an instruction to use a patched PHP version. We are continuing to monitor for any further changes or updates. The security of our products is a top priority. Docusign will continue to monitor the situation as it evolves. Please visit https://docusign.com/trust/alerts for the latest updates regarding this alert. [ORIGINAL: ‹date› ] On ‹date› Docusign became aware of a critical…

Compared with the previous archived version (#5228 to #6062). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).

Archive proof

Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this page

TodayWednesday, November 4Wed, Nov 4

1 page change

Friday, October 30

1 page change

Saturday, October 24

1 page change

Friday, October 23

1 page change

Thursday, October 22

1 page change

Cite this

Trust page changed on DocuSign’s Trust page, changed 2026-10-23 08:45 UTC (change 2 of 5).

Title
Trust page changed
Vendor
DocuSign
Date
URL
https://rewindex.com/change/p6062

All DocuSign changesDocuSign profileMarkdownJSON