Skip to main content
VulnerabilityPublished Updated

CVE-2024-8929: PHP · Information Exposure

Affects PHPSource CVE Database V5

0

Not known to be exploited · CVSS 5.8 Medium · fixed in 8.3.14 : update PHP when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.3.14, 8.2.26, 8.1.31
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade php/php-src to 8.3.14, 8.2.26 or 8.1.31.

Affected software

ProductAffectedFixed in
GitHubphp/php-srcpkg:github/php/php-srcOther threatsAffected
  • >=8.1.0 <8.1.31
  • >=8.2.0 <8.2.26
  • >=8.3.0 <8.3.14
Fixed in
  • 8.1.31
  • 8.2.26
  • 8.3.14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade PHP installations to versions 8.1.31, 8.2.26, or 8.3.14 or later, where this vulnerability is patched.
  2. Restrict MySQL server access strictly to trusted hosts and networks, minimizing exposure to potentially hostile servers.
  3. Implement network segmentation to isolate database servers from untrusted or external networks, reducing the risk of attacker-controlled MySQL servers.
  4. Monitor database client-server communications for anomalies that could indicate manipulation attempts or unexpected data leakage.
  5. For multi-tenant environments, consider additional isolation mechanisms such as separate database instances or containers per tenant to limit cross-user data exposure.
  6. Review and harden database user privileges to the minimum necessary, preventing attackers from easily establishing hostile MySQL servers.
  7. Employ runtime application self-protection (RASP) or database activity monitoring tools that can detect unusual memory access patterns or data leaks.
  8. Conduct regular security audits and penetration tests focusing on database interactions and PHP-MySQL client behavior. These steps go beyond generic patching by emphasizing network controls, monitoring, and architectural isolation to reduce attack surface and impact.

Description

In PHP versions 8.1.* before 8.1.31, 8.2.* before 8.2.26, 8.3.* before 8.3.14, a hostile MySQL server can cause the client to disclose the content of its heap containing data from other SQL requests and possible other data belonging to different users of the same server.

References

Community reviews

Loading reviews…