GCVE-1988-2026-0343
Vulnerability from gna-1988 – Published: 2026-09-11 07:55 – Updated: 2026-09-11 07:55- related CVE-2026-49953
{
"containers": {
"cna": {
"affected": [
{
"product": "Discuz!",
"vendor": "Discuz!",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Egidio Romano"
}
],
"descriptions": [
{
"lang": "en",
"value": "------------------------------------------------------\nDiscuz! \u003c= X5.0 OCR-based CAPTCHA Bypass Vulnerability\n------------------------------------------------------\n\n\n[-] Software Link:\n\nhttps://www.discuz.vip\n\n\n[-] Affected Versions:\n\nVersion X5.0, releases 20260320 through 20260610.\nOlder X3.4 and X3.5 releases may be affected too.\n\n\n[-] Vulnerability Description:\n\nA security weakness in the CAPTCHA implementation of Discuz! allows\nautomated solving of CAPTCHA challenges through Optical Character\nRecognition (OCR) techniques.\n\nDue to the limited complexity and predictability of the generated CAPTCHA\nimages, an attacker can train a custom OCR model to reliably recognize the\nchallenge text, effectively bypassing a security control intended to\nprevent automated abuse.\n\nThis issue may facilitate automated registration, login, credential\nstuffing, and exploitation workflows that rely on CAPTCHA-protected\nfunctionality.\n\n\n[-] Proof of Concept:\n\nhttps://karmainsecurity.com/pocs/discuz_captcha_bypass.zip\n\n\n[-] Solution:\n\nNo official solution is currently available.\n\n\n[-] Disclosure Timeline:\n\n[27/04/2026] - Vendor contacted through private messages on gitee.com, no\nresponse\n[27/04/2026] - Vendor contacted via e-mail at admin () discuz vip and\nsecurity () tencent com, no response\n[07/05/2026] - Opened issue IJLFUW on https://gitee.com/Discuz/DiscuzX\n[09/05/2026] - Vulnerability details shared within issue IJLFUW\n[09/05/2026] - Vendor replied \"OCR-based CAPTCHA bypass is a well-known\nissue\"\n[09/06/2026] - CVE identifier requested\n[09/06/2026] - CVE identifier assigned\n[13/06/2026] - Public disclosure at hackmeeting 0x1D\n[15/06/2026] - Publication of this advisory\n\n\n[-] CVE Reference:\n\nCVE-2026-49953 has been assigned to this vulnerability.\n\n\n[-] Credits:\n\nVulnerability discovered by Egidio Romano.\n\n\n[-] Original Advisory:\n\nhttps://karmainsecurity.com/KIS-2026-10\n\n\n[-] Technical write-up:\n\nhttps://karmainsecurity.com/chaining-bugs-in-discuz-from-race-condition-to-rce\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-09-11T07:55:56Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description",
"exploit"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jun/4"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Jun/4"
},
{
"url": "https://gitee.com/Discuz/DiscuzX"
},
{
"url": "https://karmainsecurity.com/KIS-2026-10"
},
{
"url": "https://karmainsecurity.com/chaining-bugs-in-discuz-from-race-condition-to-rce"
},
{
"url": "https://karmainsecurity.com/pocs/discuz_captcha_bypass.zip"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.discuz.vip"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Jun/4"
],
"discovery": "EXTERNAL"
},
"title": "[KIS-2026-10] Discuz! \u003c= X5.0 OCR-based CAPTCHA Bypass Vulnerability",
"x_gcve": [
{
"recordType": "analysis",
"relationships": [
{
"destId": "CVE-2026-49953",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0343",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jun/4",
"automated": true,
"contentSha256": "b57995b4e4fcb3b47cfaaa54e95919ec1b6be8469ec3fe193c4cadad9c0315ab",
"evidenceScore": 9,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Jun/4",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-06-15T18:43:10Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0343"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-11T07:55:56Z",
"dateUpdated": "2026-09-11T07:55:56Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0343"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.