CVE
Qibosoft QiboCMS unauthenticated file read in job download endpoint
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no workaround and no patch. They give no specific measure to recommend until the vendor publishes a fix.
Summary
QiboCMS V7 contains an arbitrary file download vulnerability in inc/job/download.php that allows unauthenticated attackers to read files by supplying a base64-encoded url parameter to /do/job.php?job=download. Attackers can bypass the .php extension check using the Windows 'ph<' wildcard to download sensitive files such as configuration files containing database credentials. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.
Who should check
Teams running QiboCMS V7 websites.
“QiboCMS V7 contains an arbitrary file download vulnerability”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 54 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround and no patch. They give no specific measure to recommend until the vendor publishes a fix.
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-2022-51030 (QiboCMS V7 Arbitrary File Download via job.php download endpoint), 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-2022-51030 (entry last updated 2026-11-18):
Affected:
- Qibosoft QiboCMS: versions V7
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects QiboCMS V7. (source: https://www.vulncheck.com/advisories/qibocms-v7-arbitrary-file-download-via-job-php-download-endpoint)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2022-51030 is not listed as of cve.now's last read.
This KEV status is for CVE-2022-51030 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/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/qibocms-file-download.yaml
- https://www.vulncheck.com/advisories/qibocms-v7-arbitrary-file-download-via-job-php-download-endpoint
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-2022-51030
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-2022-51030"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Qibosoft QiboCMS
V7
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2022-51030 |
| Record | NVD · CVE-2022-51030 |
| Public exploit code 3Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · PeiQi0/PeiQi-WIKI-Book · docs/wiki/cms/齐博CMS/齐博CMS V7 job.php 任意文件读取漏洞.md |
| Exploit | GitHub · qingchenhh/qc_poc · Goby/qibo_CMS_V7_job.php_file_read.go |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/qibocms-file-download.yaml |
| Other links 1 | |
| Link | vulncheck.com · advisories/qibocms-v7-arbitrary-file-download-via-job-php-download-endpoint |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2022-51030
Is CVE-2022-51030 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The job.php download endpoint in QiboCMS V7 lets a remote party download arbitrary files from the server. The source gives configuration files containing database credentials as an example of what can be read.Source: vulncheck.com
Which versions are affected by CVE-2022-51030?
QiboCMS: version V7.Source: cve.now feed data
Am I affected, and how do I check?
The reported range is QiboCMS V7, and the checked facts name no other versions or setup conditions. Compare the installed QiboCMS version with V7 to see whether it falls in that range.Source: vulncheck.com
How do I fix CVE-2022-51030?
The checked facts name no fixed version and no vendor patch, so no upgrade target can be given. Check the vendor's channels for an update that addresses this issue.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround and no patch. They give no specific measure to recommend until the vendor publishes a fix.Source: vulncheck.com