Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious script payload for makeDiy_deal.php
-
DeliveryDeliver link to admin victim
-
ExploitVictim's browser renders unsanitized input
-
ExecutionJavaScript executes in admin session
-
ImpactSteal session/perform admin actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an idccms V1.70 instance and requires user interaction (UI:R): a victim - almost certainly a logged-in administrator, given the /admin/makeDiy_deal.php path - must load the attacker-supplied payload/link for the injected script to execute. The impact is confined to script execution in the victim's browser/admin session (session theft, admin-panel actions), not direct server compromise. Limiting factors: the target endpoint sits under /admin, so a valid admin must be induced to trigger it; there is no default-configuration, unauthenticated mass-exploitation path evident, and the product's tiny deployment footprint further constrains realistic exposure. |
| Impact | This is a CWE-79 Cross-Site Scripting flaw in idccms V1.70 (/admin/makeDiy_deal.php). The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L = 7.1) reflects network reach, low complexity, no privileges, but required user interaction and a scope change - the classic profile of an XSS that executes in a victim's browser rather than compromising the server directly. The real-world signals sharply temper that score: EPSS is only 0.14% (3rd percentile), the CVE is NOT in CISA KEV, and there is no vendor patch. A public reference exists (an ants01 GitHub PoC/write-up), so publicly available exploit code exists, but this is distinct from active exploitation. Notably the A:L (availability) and I:L (integrity) impacts assigned by MITRE are generous for a reflected/stored XSS whose primary effect is limited confidentiality/integrity within the victim's authenticated admin session - a full-availability impact is not substantiated by the one-line description. Net: a low-priority, obscure-product XSS with a PoC but no evidence of real-world weaponization; the 7.1 is driven largely by the S:C and triple-impact scoring rather than demonstrated severity. |
| Exploit ScenarioDerived | An attacker crafts a malicious link or payload targeting the /admin/makeDiy_deal.php endpoint and lures an authenticated idccms administrator into loading it. When the admin's browser renders the unsanitized input, attacker-controlled JavaScript executes in the admin session context, enabling session/cookie theft or admin-panel actions on the victim's behalf. A public PoC/write-up for this exact endpoint is available on GitHub (ants01 repo). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Cross-site scripting in idccms V1.70 lets a remote, unauthenticated attacker inject script that is rendered by the administrative endpoint /admin/makeDiy_deal.php, executing in the browser of an administrator who is induced to load the crafted request or link (CVSS 3.1 base 7.1; assessed vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). The consequence is confined to script execution inside the victim's admin session - cookie/session theft, forged administrative actions, credential or token harvesting - rather than direct server compromise, and successful abuse requires both a live idccms V1.70 instance and a targeted, logged-in administrator who interacts with the payload. No active exploitation has been confirmed (the CVE is not in CISA KEV), EPSS is low at 0.14% (3rd percentile), and no public exploit code has been independently confirmed at time of analysis, though a public GitHub repository documents the flaw; the product's very small deployment footprint further limits realistic exposure.
RemediationAI
No vendor-released patch identified at time of analysis, so remediation must rely on compensating controls until an upstream fix is published. The most effective immediate step is to remove or restrict reachability of the vulnerable admin script: block external access to /admin/makeDiy_deal.php at the web server or reverse proxy (deny rules, IP allow-listing, or placing the whole /admin path behind a VPN or an authenticated reverse proxy) - the trade-off is that legitimate administrators must connect from approved networks or through the proxy. If the endpoint must remain reachable, enforce a strict Content-Security-Policy on the admin area (script-src 'self' with nonces, no 'unsafe-inline') and deploy WAF rules that normalize and reject script payloads in query parameters and POST bodies targeting /admin/makeDiy_deal.php; CSP and WAF reduce but do not eliminate exploitation because encoding bypasses and same-origin gadget chains are common. Shorten administrator session lifetimes, mark session cookies HttpOnly and SameSite=Strict, and require re-authentication before sensitive admin operations so that a successful XSS yields a narrow window for cookie theft or forged actions. Where the source is available, apply contextual output encoding (HTML entity encoding by default, JavaScript/URL encoding in the appropriate contexts) plus input validation to every user-supplied parameter consumed by makeDiy_deal.php, and treat any third-party PHP fix or commit as untrusted until the vendor ships a tagged release. Consult the NVD record (https://nvd.nist.gov/vuln/detail/CVE-2026-88746), the EUVD entry EUVD-2026-84203, and the public write-up at https://github.com/ants01/idccms-V1.70-is-vulnerable-to-XSS for reproduction details, and monitor for a vendor advisory; if idccms is not business-critical, decommissioning the instance removes the exposure entirely.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
idccms is a lightweight PHP-based content management system, and the vulnerable logic lives in its administrative back end at /admin/makeDiy_deal.php, a path that in normal deployment is reached by an authenticated administrator session. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting), meaning attacker-controlled input reaching that script is reflected or persisted into the generated HTML without adequate contextual output encoding or input sanitization, allowing the browser to interpret it as script. The assessed CVSS vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N is instructive: the attacker needs no credentials of their own (PR:N) and the flaw is trivially reachable over the network (AV:N/AC:L), but a victim must be socially induced to trigger it (UI:R), and the scope change (S:C) reflects that the impact crosses a trust boundary - out of the web application and into the administrator's browser session, where same-origin access to the admin panel enables session/cookie theft and state-changing requests. Confidentiality and integrity impacts are limited (C:L/I:L) and no availability impact is assessed. The supplied CPE data is a non-informative placeholder (cpe:2.3:a:n/a:n/a:*:*:*:*:*:*:*:*) and the EUVD affected-version list is likewise 'n/a n/a', so vendor/product resolution from NVD-style CPE cannot be relied on; version attribution comes solely from the CVE description (idccms V1.70). Cross-referencing CWE-79 with the UI:R and S:C components is what separates this from a server-side code execution issue: the payload never runs on the server, it runs in the administrator's browser and inherits that session's privileges.
Know when Idccms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Network XSS needing victim interaction (UI:R) and crossing into the browser context (S:C) with low confidentiality/integrity impact; no genuine availability impact so A:N, unlike the input's A:L.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
idccms V1.70 is vulnerable to Cross Site Scripting (XSS) in /admin/makeDiy_deal.php.
Executive ViewAI
idccms V1.70 is affected by a high-severity cross-site scripting flaw in an administrative endpoint that can let a remote, unauthenticated attacker execute script in a logged-in administrator's browser if the administrator is induced to open a crafted request or link. This could enable administrative session theft, credential or token harvesting, or forged administrative actions, but it requires a live deployment and a targeted administrator to interact with the payload, and no public exploit identified at time of analysis. Leadership should care if the organization runs idccms V1.70 because No vendor-released patch identified at time of analysis, though the product's small deployment footprint and low EPSS reduce the likelihood of broad impact.
No vendor patch: restrict access to the administrative interface and /admin/makeDiy_deal.php to trusted networks or VPN, deploy WAF or virtual patching rules to block XSS against that endpoint, enforce MFA and short admin session timeouts, train administrators not to click untrusted links while authenticated, monitor admin sessions for anomalous or forged actions, and isolate or decommission idccms V1.70 where feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/dbBakMySQL_deal.php?
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/serverFile_deal.php?
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/softBak_deal.php?mud
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/softBak_deal.php?mud
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userGroup_deal.php?m
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userScore_deal.php?m
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userGroup_deal.php?m
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userLevel_deal.php?m
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via admin/info_deal.php?mudi=ad
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/infoSys_deal.php?mud
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/userSys_deal.php?mud
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/keyWord_deal.php?mud
EUVD-2026-84203
GHSA-vqrr-hcgq-2p5v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB