🛡️ CVE-2018-16650 — phpmyfaq

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-352 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

phpMyFAQ CSRF

phpMyFAQ before 2.9.11 allows CSRF.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Weakness class

CVE-2018-16650 is classified as CWE-352: Cross-Site Request Forgery (CSRF). A state-changing request is accepted without proof it was intended, so another site can trigger it using the victim's session.

Affected software

CVE-2018-16650 is recorded against 1 package.

  • thorsten/phpmyfaq (fixed in 2.9.11)

Timeline and source

Published on 14 May 2022 and last revised on 16 February 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Advisory)
github.com (Package)
www.phpmyfaq.de (Web)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CWE CWE-352
Public Exploit ✅ No
Source OSV
Published 2022-05-14
Updated 2026-08-12
Modified 2024-02-16
Fix URL N/A

Affected Packages

Software From version Fixed in
thorsten/phpmyfaq — 2.9.11

Similar Threats

Site Security Check

Is phpmyfaq part of your stack?

CVE-2018-16650 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.