PHP Script Security Rewrite - 24/05/2026 05:28 EDT

I have a custom-built PHP script that was originally ported from the ViserLab code-base. Its core job is data processing and manipulation, and it currently functions as expected. However, several ViserLab-specific sections still remain. I need every reference, include, or snippet tied to that original package removed or replaced with my own custom code so the application becomes fully standalone—yet keeps identical behaviour from a user’s point of view.

While doing this refactor, the main priority is hardening the script against unauthorized access. Please treat the review as a security audit: follow common PHP security best practices, check session handling, privilege boundaries, and ensure any file or database operations cannot be abused. No changes are required to the business logic itself; the focus is on access control and replacing legacy fragments.

Deliverables
• Clean, fully working PHP codebase with all ViserLab remnants replaced by custom implementations
• A brief security report outlining the issues found and the measures taken to close each gap
• Updated configuration or installation notes so I can deploy the new version without surprises

I will provide the current repository and a short walkthrough of its workflow. After your changes I’ll run the usual functional tests; if everything behaves the same and the security report looks solid, the job is complete.