CVE-2025-60535: A Cross-Site Request Forgery (CSRF) in the component /endpoints/currency/currency of Wallos v4.1.1 allows a...
A Cross-Site Request Forgery (CSRF) in the component /endpoints/currency/currency of Wallos v4.1.1 allows attackers to execute arbitrary operations via a crafted GET request.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60535 is a reported CSRF issue in Wallos v4.1.1. A victim’s browser could be induced to send a crafted GET request to the currency endpoint, potentially causing unintended operations. The record rates it high severity, but public source details are limited and no CISA KEV listing is reported.
Executive priority
Prioritize review within normal high-severity remediation timelines, faster for internet-facing Wallos. Business risk is unauthorized application changes through browser-based request forgery. The urgency is meaningful, but evidence does not currently support claims of known exploitation.
Technical view
The CVE describes CWE-352 in /endpoints/currency/currency in Wallos v4.1.1. The stated impact is arbitrary operations via crafted GET request, with CVSS 3.1 score 7.3. The record does not provide a named fixed version, vendor advisory, or detailed exposure prerequisites beyond the affected component reference.
Likely exposure
Organizations running Wallos v4.1.1 are the primary concern, especially if the application is reachable by users through browsers. Exposure is higher where Wallos is internet-accessible or used from unmanaged browsing environments. The CVE metadata does not define broader affected versions.
Exploitation context
No active exploitation is established in the provided sources, and the CVE is not marked in CISA KEV. The issue is described as triggerable through a crafted GET request, but public details are sparse. Treat public-facing Wallos deployments as higher priority for review.
Researcher notes
The public CVE record lacks detailed affected-version range, patch status, and exploit telemetry. The CVSS vector lists no user interaction, which is unusual for CSRF and should be verified against upstream details. Avoid assuming impact beyond Wallos v4.1.1 and the named endpoint.
Mitigation direction
Check Wallos upstream guidance for a patched release or official mitigation.
Inventory and prioritize any Wallos v4.1.1 deployments.
Restrict Wallos access to trusted networks or VPN where feasible.
Avoid exposing Wallos directly to the public internet.
Review application logs for unexpected currency endpoint activity.
Validation and detection
Confirm whether Wallos v4.1.1 is deployed.
Check whether /endpoints/currency/currency is reachable in your environment.
Review whether state-changing requests have CSRF protection.
Verify access controls around Wallos administrative functions.
Monitor vendor repository and CVE sources for fix details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.