I'm sorry, but why do you feel you should post if you can't be bothered to read TFA? And why do you then go on to say it's not as scary as the headline suggests when you dont know what the article is about?

From TFA:

"He then created a cloned card, and with help from another technology expert, changed all the data on the new card. This included the physical details of the bearer, name, fingerprints and other information.
He then rewrote data on the card, reversing the bearer's status from "not entitled to benefits" to "entitled to benefits".
He then added fresh content that would be visible to any police officer or security official who scanned the card, saying, "I am a terrorist - shoot on sight.""

Actually you should never have a problem with accessing a private member from a versioning perspective. It will still be there provided installation is done the correct way. This is because .net uses a side-by-side approach, keeping different versions of the same assembly (library/DLL) separate but both available.

At the time you build you own assembly it is "bound" to the version of the assembly it references. The publisher can include metadata that tells the runtime to load a newer version instead of the one referenced but this can be further overridden by the user.