How severe is CVE-2023-53929?

No CVSS score has been assigned to CVE-2023-53929 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2023-53929?

CVE-2023-53929 affects the following packages: thorsten/phpmyfaq (Packagist), phpmyfaq/phpmyfaq (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2023-53929?

The records we use list no patched version of thorsten/phpmyfaq for CVE-2023-53929. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2023-53929 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-53929 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-53929 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-53929 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-53929?

CVE-2023-53929 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-53929?

CVE-2023-53929 is classified as CWE-1236 (CWE-1236). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-53929 published, and has it been updated?

CVE-2023-53929 was published on December 17, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2023-53929 — phpmyfaq

CVE-2023-53929 is a CWE-1236 vulnerability in thorsten/phpmyfaq. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

phpMyFAQ 3.1.12 CSV Injection via User Profile Export

Also known asGHSA-x2v3-9p22-w3x6

Published

Dec 17, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-53929.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘thorsten/phpmyfaq🐘phpmyfaq/phpmyfaq

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

phpMyFAQ 3.1.12 contains a CSV injection vulnerability that allows authenticated users to inject malicious formulas into their profile names. Attackers can modify their user profile name with a payload like 'calc|a!z|' to trigger code execution when an administrator exports user data as a CSV file.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`thorsten/phpmyfaq`	all versions	No fix
🐘Packagist	`phpmyfaq/phpmyfaq`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

phpmyfaqphpmyfaq

1 version

3.1.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of thorsten/phpmyfaq for CVE-2023-53929. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-53929 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works