Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious intermediary page
-
DeliveryLure victim to submit POST with crafted Referer
-
ExploitReferer reflected unescaped in index.php response
-
ExecutionScript executes in victim browser session
-
ImpactSession/data theft in user context
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 | Requires the CuteNews 2.1.2 index.php POST-handling path where the Referer header is copied into the response HTML unescaped. Practical exploitation is limited by three factors: the attacker must induce a victim to trigger a POST request (UI:R) whose Referer header carries the payload - and because browsers populate Referer automatically from the originating page rather than from attacker-supplied links, the attacker typically needs an attacker-controlled or same-site intermediary page to shape the Referer value (the basis for AC:H). No authentication is required (PR:N), but no working exploitation occurs against a passive victim without the crafted delivery context. |
| Impact | This is a genuinely low-priority reflected XSS despite its 5.8 (Medium) CVSS rating. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L is network-reachable and unauthenticated (PR:N), but two metrics heavily constrain real-world risk: AC:H and UI:R. Critically, the injection sink is the HTTP Referer header, which a victim's browser sets automatically based on the originating page and which an attacker cannot arbitrarily control in a normal cross-site drive-by - this justifies AC:H and makes practical exploitation awkward (typically requiring a same-site or attacker-hosted intermediary page, or a client that permits Referer manipulation). All exploitation signals point the same direction: EPSS is 0.14% (4th percentile - very low predicted exploitation), the CVE is NOT in CISA KEV, and no verified public exploit code is identified (a third-party 'CVEs-2026-Disclosure' GitHub repo is referenced but its contents are not confirmed as working POC here). No signals conflict; every independent source agrees this is a low-urgency, low-impact reflected XSS. The main caveat is data quality rather than severity: the CPE ('cpe:2.3:a:n/a:n/a:*') and affected-version fields ('n/a n/a') are placeholder junk, so automated version-based detection is unreliable and the affected scope rests solely on the description naming CuteNews v2.1.2. |
| Exploit ScenarioDerived | An attacker crafts a page or request flow that causes a victim's browser to submit a POST to the CuteNews index.php with an attacker-influenced Referer header containing a script payload, which is reflected unescaped into the response and executes in the victim's session. Because the payload rides in the Referer header rather than a directly clickable URL parameter, the attacker must set up an intermediary/hosted context and rely on user interaction (UI:R, AC:H), making delivery non-trivial. No verified public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Reflected cross-site scripting (XSS) in CuteNews 2.1.2 allows the value of the HTTP Referer header to be copied, unescaped, into the HTML response generated when POST messages are submitted to index.php, so a crafted Referer value can execute JavaScript in a victim's browser under the site's origin. No authentication is required (PR:N), but exploitation depends on user interaction (UI:R) and on an attacker-controlled or same-site intermediary page that shapes the Referer value, which is why the assessed vector carries AC:H; browsers set Referer automatically rather than from attacker-supplied links, so a passive victim cannot be triggered without the crafted delivery context. Independent assessment rates this a genuinely low-priority reflected XSS, EPSS is only 0.14% (4th percentile), and no public exploit code has been identified at time of analysis; there is no confirmed CISA KEV active exploitation.
RemediationAI
No vendor-released patch has been identified at time of analysis, so remediation must start with confirming whether the maintainer has published a fixed build beyond 2.1.2; consult the project repository at https://github.com/CuteNews/cutenews-2.0 and the disclosure record at https://github.com/UmbraDeorum/cutenews-2.0-CVEs-2026-Disclosure, and track the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-36470 for an updated reference. Because the fix is simply output encoding, the most effective immediate mitigation is to patch or hot-fix the index.php POST-message path so that the Referer header is passed through htmlspecialchars()/htmlentities() (or an equivalent contextual encoder) before being written into the response; the trade-off is that any templates referencing that value must expect entity-encoded output. As compensating controls, send a Referrer-Policy header (for example no-referrer or same-origin) on the CuteNews instance to reduce the attacker's ability to shape the Referer value, and/or send a strict Content-Security-Policy that blocks inline and untrusted script sources so a reflected payload cannot execute; note that a restrictive CSP can break legitimate third-party widgets, scripts and inline handlers. Where POST message handling is not required, disabling or restricting that feature in index.php removes the vulnerable path entirely, at the cost of losing that functionality, and deploying the application behind a WAF or reverse proxy that normalizes/escapes unsafe Referer values provides only partial, bypassable protection. Finally, since exploitation requires victim interaction, session-cookie hardening (HttpOnly, SameSite) limits the consequences of a successful reflected XSS but does not prevent the injection itself.
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
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting) in CuteNews 2.1.2's index.php: the application reflects the client-supplied Referer request header into its generated HTML without output encoding or escaping, in the code path that handles POST messages. CuteNews is a PHP-based news/blog management script, and the tags mark this as a PHP web application issue. The CVSS v3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L describes a network-reachable, unauthenticated flaw that is complicated to trigger (AC:H) because the attacker generally cannot set an arbitrary Referer header directly on a victim's browser request; an attacker-controlled or same-site intermediary page is typically needed to stage the payload, and the victim must still perform an interaction (UI:R). The changed scope (S:C) reflects that the exploited component (the CuteNews server reflecting unescaped input) differs from the impacted component (the victim's browser session, where attacker script runs in the site origin). Impact is limited to low confidentiality, integrity and availability sub-scores, consistent with a reflected XSS whose practical effect is script execution in the victim's context rather than server-side compromise. The supplied CPE string is unpopulated (cpe:2.3:a:n/a:n/a), so the precise affected build must be taken from the vendor/community references (https://github.com/CuteNews/cutenews-2.0 and the disclosure repository https://github.com/UmbraDeorum/cutenews-2.0-CVEs-2026-Disclosure) rather than from automated CPE mapping.
Know when Cutenews 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:H/PR:N/UI:R/S:C/C:L/I:L/A:L
Referer header is not directly attacker-controllable so AC:H; reflected XSS needs victim interaction (UI:R), no auth (PR:N), and executes in browser context crossing scope (S:C) with limited C/I/A.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
CuteNews v.2.1.2 is vulnerable to Cross Site Scripting (XSS) in index.php. The value of the "Referer" header is copied into the response HTML unmodified/unescaped during POST messages to index.php.
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.
An issue was discovered in CutePHP CuteNews 2.1.2. Rated high severity (CVSS 8.8), this vulnerability is remotely exploi
Server-side request forgery in CuteNews 2.1.2 (core/modules/media.php, the Media Manager 'Upload by URL' handler upload_
CuteNews 2.0.1 allows remote authenticated attackers to execute arbitrary PHP code via unspecified vectors. Rated high s
Reflected cross-site scripting in CuteNews 2.1.2 allows remote unauthenticated attackers to execute arbitrary JavaScript
Cross-site scripting vulnerability in CuteNews 2.0.1 allows remote attackers to inject arbitrary web script or HTML via
PHP object injection in CuteNews 2.1.2 allows remote attackers to overwrite internal request variables - including __ref
Reflected cross-site scripting (XSS) in CuteNews 2.1.2 allows an unauthenticated remote attacker to inject a javascript:
EUVD-2026-83992
GHSA-29r2-83fr-44fv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB