Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • From Pair support:

    “Back in 2012 there was a massive PHP vulnerability that was
    discovered that was present in all versions of PHP, both current (for May
    2012 current that is) and all previous versions. Information on this bug
    can be found at the link below.

    https://bugs.php.net/bug.php?id=61910

    When the bug was discovered, there were no immediate patches
    available. As a work-around, pair Networks gave every domain we host
    special lines in an .htaccess file to secure users against this issue.
    About a week after the bug was discovered, patches were available and all
    versions of PHP on our servers were updated, but the .htaccess file lines
    were left in place as they were not causing any issues.

    As PHP has long since been patched, these lines are no longer
    needed, so commenting them out (disabling the specific lines) poses no
    threat to security.”

    Hi, David.

    I ran into this exact same problem with my site, also hosted on Pair. After a good amount of digging, I found that the core issue was that a number of the JS calls that pull up the visual editor were returning 403, and it apparently had something to do with the query strings appended to the calls.

    Anyway, I contacted Pair support, they responded thusly:
    “I believe that this was likely caused by an emergency fix that was put in place to stop a PHP vulnerability in May of 2012. I’ve commented out the emergency fix, which has been patched, and I can now view the contents of that file.”

    And I’ve verified that the visual editor now comes up. You may want to contact Pair support as well.

Viewing 2 replies - 1 through 2 (of 2 total)