CVE
QPixel information disclosure in unscoped comment lookup
- Exploited
- No known exploitation
- Fix
- Fixed in 0.13.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.13.0.
Summary
Codidact's QPixel, a Q&A community software, has a flaw that lets a remote attacker read comments without logging in. By enumerating sequential comment IDs, the attacker can view the full content of comments from other communities, soft-deleted comments, and comments in access-restricted categories.
Original description
QPixel is a Q&A-based community knowledge-sharing software. Prior to 0.13.0, the unauthenticated comments#show action in app/controllers/comments_controller.rb resolves user-controlled comment IDs with Comment.unscoped, bypassing the Comment community default scope, and performs no deletion or post-visibility authorization check. A remote unauthenticated attacker can enumerate sequential IDs and read the full content of comments belonging to other communities, soft-deleted comments, and comments under access-restricted categories. The JSON response exposes the stored comment columns because the model has no limiting as_json override. This issue is fixed in version 0.13.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.13.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-68522 (QPixel: Unauthenticated cross-community comment disclosure via Comment.unscoped bypassing tenant and deletion checks), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-68522 (entry last updated 2026-11-18):
Affected:
- codidact qpixel: fixed in 0.13.0
Fixed versions: 0.13.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-68522 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68522 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/codidact/qpixel/security/advisories/GHSA-9mhx-jr3h-2cvf
- https://github.com/codidact/qpixel/pull/2080
- https://github.com/codidact/qpixel/commit/78240c7bca374b50047455bade7f3596887ee782
- https://github.com/codidact/qpixel/commit/d4d49b640c4b70f931e84a1d137acb93a1703867
- https://github.com/codidact/qpixel/releases/tag/v0.13.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-68522
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68522"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- codidact qpixel
fixed in 0.13.0
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · codidact/qpixel · Advisory GHSA-9mhx-jr3h-2cvf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-68522 |
| Record | NVD · CVE-2026-68522 |
| Other links 4 | |
| Repository | GitHub · codidact/qpixel · Pull request #2080 |
| Repository | GitHub · codidact/qpixel · Commit 78240c7b |
| Repository | GitHub · codidact/qpixel · Commit d4d49b64 |
| Repository | GitHub · codidact/qpixel · Release v0.13.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-68522
Is CVE-2026-68522 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-68522?
qpixel: before 0.13.0.Source: cve.now feed data
How do I fix CVE-2026-68522?
Upgrade to a fixed version: 0.13.0.Source: cve.now feed data