Security readout for executives and security teams
Plain-English summary
phpMyFAQ before 4.0.18 can let anyone on the network create active user accounts through a WebAuthn preparation API. This can happen even when normal registration is disabled. The main business risk is unauthorized account proliferation and integrity impact in the FAQ platform.
Executive priority
Prioritize remediation for any internet-facing phpMyFAQ deployment. The flaw does not directly expose data per the CVSS vector, but it undermines account control and could enable follow-on abuse inside the application.
Technical view
CVE-2026-27836 is a CWE-862 missing authorization flaw in phpMyFAQ < 4.0.18. The /api/webauthn/prepare endpoint could create active users without authentication, CSRF protection, captcha, or configuration checks. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges or user interaction required.
Likely exposure
Organizations running internet-accessible or internal phpMyFAQ instances below 4.0.18 are potentially exposed. Exposure is higher where the application is reachable by untrusted users. The source data does not identify affected managed services or downstream packaged versions.
Exploitation context
The vendor advisory describes unauthenticated account creation through a reachable API endpoint. The record is not marked as CISA KEV, and the provided sources do not state active exploitation in the wild.
Researcher notes
The public description centers on account creation, not privilege escalation after account creation. Assess real-world impact by reviewing phpMyFAQ role defaults and local workflow, but do not assume administrative access unless confirmed in the environment or vendor documentation.
Mitigation direction
- Upgrade phpMyFAQ to version 4.0.18 or later.
- Review vendor advisory and release notes for environment-specific guidance.
- Inventory all phpMyFAQ instances, including internal deployments.
- Review and remove unauthorized or unexpected user accounts.
- If upgrade is delayed, seek vendor-supported compensating controls.
Validation and detection
- Confirm each phpMyFAQ instance version is 4.0.18 or later.
- Check whether /api/webauthn/prepare is reachable from untrusted networks.
- Review user creation logs around the disclosure window.
- Compare current user list against approved account records.
- Verify registration settings after upgrade remain as intended.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27836 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-w22q-m2fm-x9f4CVE reference · x_refsource_CONFIRM
- https://github.com/thorsten/phpMyFAQ/commit/f2ab673f0668753cd0f7c7c8bc7fd2304dcf5cb1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.