CVE-2026-130342 in phpMyFAQinfo

Summary

by MITRE • 11/17/2026

phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper reference counting flaw on multisite deployments, allowing editors to delete other instances' attachment files. Because linkedRecords() counts only the local faqattachment table, deleting an attachment with shared md5 content makes File::delete() unlink the shared blob, destroying another instance's files.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/17/2026

The vulnerability identified in phpMyFAQ versions prior to 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 represents a critical logic flaw within the application’s attachment management subsystem, specifically affecting multisite deployments where multiple instances share underlying storage resources. This issue stems from an improper reference counting mechanism that fails to account for cross-instance dependencies when managing file deletions. In environments configured with shared databases or centralized media repositories, different phpMyFAQ installations may host content that references identical binary files based on their MD5 hash values rather than unique identifiers. The core technical failure occurs within the linkedRecords() function, which is responsible for determining how many active records still reference a specific attachment file before it can be safely removed from disk.

The operational flaw lies in the fact that linkedRecords() only queries the local faqattachment table of the current instance to determine usage counts. It does not inspect other instances within the same multisite network or shared storage environment for references to files with matching MD5 hashes. Consequently, when an editor deletes an attachment from one site, the system calculates a reference count based solely on that specific installation's database entries. If another phpMyFAQ instance holds a record pointing to a file with the exact same content and thus the same hash, this external dependency is ignored by the deletion logic. The application proceeds to call File::delete(), which unlinks the shared blob from the filesystem under the false assumption that no other records depend on it.

This improper reference counting leads directly to data loss for administrators of other instances sharing the storage infrastructure. When a user deletes an attachment in one context, they inadvertently destroy files required by another distinct phpMyFAQ installation. This results in broken links, missing media assets, and potential corruption of knowledge base content across the entire multisite deployment. The impact is particularly severe because it allows any authenticated editor to cause destructive side effects outside their own site's scope without explicit permission or awareness, violating the principle of isolation between tenant instances.

From a classification perspective, this vulnerability aligns with CWE-672, which describes the use of externally controlled references for resources and actions that can result in unintended information disclosure or modification due to improper reference counting. It also relates to CWE-829, concerning inclusion of functionality from outside the control sphere, as the application fails to validate dependencies across administrative boundaries it should be managing. In terms of MITRE ATT&CK mapping, this behavior reflects techniques associated with Impact and Defense Evasion, specifically where an actor leverages shared infrastructure weaknesses to cause denial of service or data destruction against other tenants in a multi-tenant architecture.

Mitigation strategies must focus on updating the application to version 4.1.12 or later for stable releases, or 4.2.0-RC.2 and above for alpha versions, where this reference counting logic has been corrected to account for shared resources. Administrators operating multisite deployments should ensure that their database queries are scoped correctly to include all relevant instances when calculating attachment usage statistics. Additionally, implementing strict isolation of media storage per instance or using unique file naming conventions based on UUIDs rather than relying solely on content-based hashing can prevent accidental cross-instance data loss in legacy configurations until patches are applied. Regular audits of shared filesystem permissions and database integrity checks are also recommended to detect any residual damage caused by this flaw prior to remediation.

Responsible

VulnCheck

Reservation

11/17/2026

Disclosure

11/17/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!