Skip to content
Noroxi
NVD / CVE Program· CNA VulnCheck

CVE-2026-46366: phpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission Bypass

HighCVSS 8.7 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 34/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: thorsten phpmyfaq 4.1.2.

Low priority for now. Upgrade to thorsten phpmyfaq 4.1.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

phpMyFAQ before 4.1.2 contains an information disclosure vulnerability in the getIdFromSolutionId() method that lacks permission filtering, allowing unauthenticated attackers to enumerate restricted FAQ entries and read their titles via the /solution_id_{id}.html endpoint. Attackers can sequentially iterate solution IDs to discover all FAQs including those restricted to specific users or groups, leaking sensitive metadata through redirect Location headers and page canonical links.

Published
May 15, 2026
Updated
Nov 8, 2026
EPSS
0.3% · 27th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulnCheck
7.5
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46366

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

  • thorsten phpmyfaq

    • 4.1.2not affected
    • before 4.1.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistphpmyfaq/phpmyfaqbefore 4.1.24.1.2
Packagistthorsten/phpmyfaqbefore 4.1.24.1.2

Other highest-scoring records for the same primary product.

  • CVE-2026-46364phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha
    38Monitor
  • CVE-2026-111911phpMyFAQ 4.0.0 before 4.1.9 Authentication Bypass via WebAuthn Credential Injection
    37Monitor
  • CVE-2026-66398phpMyFAQ before 4.1.6 Remote Code Execution via Configuration API
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-46363May 15, 2026 · phpMyFAQ - Stored XSS in FAQ Question/Answer via Encode-Decode Bypass
    20Monitor
  • ← EarlierCVE-2026-46365May 15, 2026 · phpMyFAQ - Missing Authorization in Tag Deletion Endpoint
    21Monitor
  • Later →CVE-2026-46367May 15, 2026 · phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
thorsten phpmyfaq4.1.2Vendor (CNA)
Packagist:phpmyfaq/phpmyfaq4.1.2Package registry (OSV)
Packagist:thorsten/phpmyfaq4.1.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-463620 days apartphpMyFAQ - Authorization Bypass in Admin Pages via Non-Terminating Permission Check
    28Monitor
  • CVE-2026-124433177 days apartphpMyFAQ before 4.1.11 Insufficient Authorization in Group Deletion via GroupController
    28Monitor
  • CVE-2026-85592112 days apartphpMyFAQ before 4.1.8 Authorization Bypass via question/create
    25Monitor
  • CVE-2026-450090 days apartphpMyFAQ - Insufficient Authorization Check in Admin API Endpoints
    21Monitor
  • CVE-2026-85587112 days apartphpMyFAQ before 4.1.8 Incorrect Authorization via Admin Pages
    21Monitor
  • CVE-2026-111900155 days apartphpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Draft FAQ Attachment Disclosure via attachment.php
    21Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records