Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-33135: Reflected XSS in WeGIA novo_memorandoo.php

Published Mar 20, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.1Medium · v3.1
EPSS0.26%18th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wegia
IdentifiersCVE-2026-33135CWE-79 · Improper Neutralization of Input…

CVE-2026-33135 is a reflected cross-site scripting vulnerability in WeGIA, a web manager for charitable institutions. The issue affects WeGIA 3.6.6 and earlier and is present in the /html/memorando/novo_memorandoo.php endpoint. The vulnerable code reads HTTP GET parameters to display dynamic success messages and, when $_GET['msg'] is equal to 'success', directly concatenates attacker-controlled input from $_GET['sccs'] into an HTML alert <div> that is returned to the browser without sanitization or output encoding. This allows arbitrary JavaScript supplied in the sccs parameter to be reflected into the response and executed in the victim's browser in the context of the WeGIA application.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows execution of arbitrary JavaScript in the victim user's browser within the security context of the vulnerable WeGIA application. This can enable theft of session tokens or other sensitive browser-accessible data, unauthorized actions on behalf of the victim, manipulation of application content, and other client-side compromise effects. The provided CVSS v3.1 vector indicates high confidentiality and integrity impact, no direct availability impact, and changed scope due to browser-side execution affecting the user context.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, avoid reflecting untrusted GET parameters such as sccs into HTML responses, especially in success or status message rendering paths. Apply strict server-side output encoding for any user-controlled data before insertion into HTML, and consider adding or tightening a Content Security Policy to reduce script execution impact. User interaction is required for exploitation, so reducing exposure of crafted links and monitoring for suspicious requests to /html/memorando/novo_memorandoo.php with msg=success and script-like sccs values may help detect or limit abuse, but these measures are not substitutes for patching.

Remediation

Patch, then assume compromise.

Upgrade WeGIA to version 3.6.7 or later, where the issue is fixed. The vulnerable behavior in novo_memorandoo.php should be corrected by ensuring that untrusted data from the sccs parameter is not inserted into HTML output without proper context-appropriate escaping or encoding. Review similar code paths that build success or status messages from request parameters and apply consistent output encoding and input handling controls.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WegiaWegiaapplication
FAQ

Frequently asked questions

Is CVE-2026-33135 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2026-33135 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33135?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2026-33135.
Is there a patch for CVE-2026-33135?
Upgrade WeGIA to version 3.6.7 or later, where the issue is fixed. The vulnerable behavior in novo_memorandoo.php should be corrected by ensuring that untrusted data from the sccs parameter is not inserted into HTML output without proper context-appropriate escaping or encoding.
What products are affected by CVE-2026-33135?
Wegia.
How severe is CVE-2026-33135?
CVE-2026-33135 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 0.26% (18th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.