Urgent Help Needed: OJS 3.3.0-13 Under Attack and Cannot Upgrade

Dear PKP Community,

I urgently need assistance regarding a security issue with my OJS installation. I am currently using OJS 3.3.0-13, and my journal website has been repeatedly compromised. Malicious code is being injected into the system — including modifications to the index.php file inside the public_html directory — resulting in strange or unrelated words appearing in Google search results for my site.

Even after manually removing the injected content, it reappears shortly after. It seems the attacker has persistent access. I understand that this version is outdated, but I have not been successful in upgrading directly to the latest OJS version due to compatibility and system constraints.

My key questions are:

  1. How can I secure my current OJS installation immediately to stop the ongoing attack?
  2. What is the safest upgrade path from OJS 3.3.0-13 to the latest stable version?
  3. Are there any specific steps I should follow to clean the installation and verify file integrity before attempting an upgrade?
  4. Should I consider a fresh installation and migrate the database and files manually? If so, what is the safest method?
  5. Can I simply export my issues and articles and them import them in new installation? But this gives locale error while importing.

This situation is urgent, as my journal’s reputation and indexing are at risk. Any guidance or support from the community or PKP team would be deeply appreciated.

Best regards,
Pankaj

Hi @Pankaj_Kumar,

There are several known cross-site scripting vulnerabilities that exist in older 3.3.0-x releases, particularly before 3.3.0-15. These are fixed in the latest 3.3.0-x release, which should be a quick and easy upgrade without any changed system requirements/constraints. I would recommend upgrading to the latest 3.3.0-x release and performing the cleanup needed to remove any malicious scripting etc.; continuing to re-install 3.3.0-13 will not prevent the same attack from occurring again.

Regards,
Alec Smecher
Public Knowledge Project Team