LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3766: Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq

Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.8.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-3766 is a reflected cross-site scripting issue in thorsten/phpmyfaq before version 3.1.8. A vulnerable site could reflect attacker-controlled content into a user’s browser, risking session or data exposure depending on site context. The public sources do not show confirmed active exploitation.

Executive priority

Treat this as a high-priority application patch for any public phpMyFAQ instance. The business urgency is strongest where phpMyFAQ handles authenticated users, internal knowledge, or customer-facing traffic.

Technical view

The CVE records CWE-79 reflected XSS in the GitHub repository thorsten/phpmyfaq prior to 3.1.8, with CVSS 3.0 score 7.3. The fix reference is an upstream commit. A public PoC reference exists, but the bundle does not establish weaponized or active exploitation.

Likely exposure

Exposure is limited to organizations running phpMyFAQ versions earlier than 3.1.8, especially internet-facing FAQ deployments. The bundle does not identify affected configurations beyond the product and pre-3.1.8 version range.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. Public vulnerability and PoC references exist, so defenders should assume discoverability, but there is no cited evidence here of active exploitation in the wild.

Researcher notes

Evidence supports reflected XSS, CWE-79, affecting thorsten/phpmyfaq before 3.1.8. The supplied CVSS vector unusually lists UI:N for XSS; rely on vendor and CVE data, and avoid assuming exploit mechanics beyond the public references.

Mitigation direction

  • Upgrade phpMyFAQ to version 3.1.8 or later after reviewing upstream guidance.
  • Confirm the deployed code includes the referenced upstream fix commit.
  • Prioritize remediation for internet-facing phpMyFAQ deployments.
  • If upgrade is delayed, check vendor guidance for supported temporary mitigations.
  • Restrict access to vulnerable deployments where business operations allow.

Validation and detection

  • Inventory all phpMyFAQ deployments and record exposed URLs and versions.
  • Verify whether each deployment is earlier than phpMyFAQ 3.1.8.
  • Confirm patched deployments include the upstream fix or an equivalent vendor release.
  • Review web logs for unusual reflected-input activity around public phpMyFAQ pages.
  • Use safe staging validation rather than production exploit testing.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cve · low confidence lookup

CVE-2022-3766 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.3High
CVSS 3.0 vector shape for CVE-2022-3766Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
thorstenthorsten/phpmyfaqunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.