CVE-2026-130369: Inventory and update phpMyFAQ deployments
The phpMyFAQ team disclosed CVE-2026-130369 on November 16, 2026. Its security bulletin identifies 4.1.12 and 4.2.0-RC.2 as corrective releases. The download page recommends stable 4.1.12 for production and labels 4.2.0-RC.2 as testing-only.
The maintainer labels the issue High. VulnCheck’s CNA record, published November 17, rates it CVSS 4.0 score 9.2, Critical, and CVSS 3.1 score 8.1, High. Preserve that attribution rather than treating the ratings as interchangeable.
Select the patch for the installed branch
The CNA lists stable versions from 4.1.9 up to, but excluding, 4.1.12 as affected. It separately lists the prerelease range from 4.2.0-alpha up to, but excluding, 4.2.0-RC.2. It records 4.1.12 and 4.2.0-RC.2 as unaffected.
For an affected stable deployment, select 4.1.12 or a later supported stable release containing the fix. Keep prerelease testing separate from production. If an older installation falls outside the CNA’s stated range, establish its support and upgrade path with the project instead of treating the range as a general assurance about old software.
Inventory each instance
Record the application version and deployed package identity for each phpMyFAQ instance, including client instances in a multisite deployment. Check the installation selected by the web server and the package record on every serving node.
Keep the PHP runtime version as a separate inventory item. Updating PHP alone does not replace the phpMyFAQ application package. For deployments built into images, record the running digest and the application version in the corresponding build manifest.
Upgrade and check normal operation
Back up the database, application configuration and uploaded content before maintenance. Follow the project’s documented update procedure for the starting version and confirm package prerequisites before replacing files.
After the update, compare the deployed application with the approved release on each node. Use an existing authorized account for an ordinary sign-in and read-only FAQ check in each instance. Review normal application logs for migration or startup errors.
Retain the package version, artifact identity and validation result in the change record. Keep an instance pending until its active deployment is confirmed; a downloaded archive or updated build template is not evidence that a running instance changed.
Acknowledgements
This post was created with assistance from AI.