Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62113: CWE-352 Cross-Site Request Forgery (CSRF) in emendo_seb Co-marquage service-public.fr

0
Medium
VulnerabilityCVE-2025-62113cvecve-2025-62113cwe-352
Published: Wed Dec 31 2025 (12/31/2025, 16:28:24 UTC)
Source: CVE Database V5
Vendor/Project: emendo_seb
Product: Co-marquage service-public.fr

Description

Cross-Site Request Forgery (CSRF) vulnerability in emendo_seb Co-marquage service-public.Fr allows Cross Site Request Forgery.This issue affects Co-marquage service-public.Fr: from n/a through 0.5.77.

AI-Powered Analysis

AILast updated: 01/20/2026, 22:26:00 UTC

Technical Analysis

CVE-2025-62113 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the emendo_seb Co-marquage service-public.fr product, affecting versions up to 0.5.77. CSRF vulnerabilities occur when a web application does not adequately verify that requests originate from legitimate users, allowing attackers to craft malicious web pages or links that cause authenticated users to unknowingly perform unwanted actions. In this case, the vulnerability permits an attacker to induce a user to submit a forged request to the Co-marquage service, potentially altering data or triggering unauthorized operations. The CVSS vector indicates the attack can be performed remotely (AV:N) with low complexity (AC:L), requires no privileges (PR:N), but does require user interaction (UI:R). The impact is limited to integrity (I:L), with no confidentiality or availability impact. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and assigned a medium severity rating. The affected product is a French public sector co-branding service, suggesting its use primarily within government or affiliated organizations. The lack of authentication requirements for the attacker and the need for user interaction are typical for CSRF issues, emphasizing the need for proper anti-CSRF protections such as tokens or same-site cookie attributes. The vulnerability was reserved in October 2025 and published at the end of 2025, indicating recent discovery and disclosure.

Potential Impact

For European organizations, particularly those in France's public sector using the Co-marquage service-public.fr platform, this vulnerability could lead to unauthorized modification of data or execution of unintended actions within the affected service. While confidentiality and availability are not impacted, integrity compromise could undermine trust in official documents or processes managed through the platform. Attackers could exploit this to manipulate co-branding operations or related administrative functions, potentially causing reputational damage or operational disruptions. Given the public sector focus, the impact could extend to citizens relying on government services, affecting service delivery and compliance with regulatory standards. The requirement for user interaction limits large-scale automated exploitation but targeted phishing or social engineering campaigns could still pose a significant risk. Organizations across Europe that integrate or interface with this service might also be indirectly affected if they rely on data or services from the vulnerable platform.

Mitigation Recommendations

To mitigate CVE-2025-62113, organizations should implement robust anti-CSRF protections such as synchronizer tokens or double-submit cookies to ensure that all state-changing requests are validated for authenticity. Enforcing the use of SameSite=strict or lax cookie attributes can reduce the risk of CSRF by restricting cross-origin requests. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF attempts. User education campaigns should inform users about the risks of clicking unknown or unsolicited links, especially when authenticated to sensitive services. Monitoring and logging of unusual request patterns can help detect exploitation attempts early. Since no official patches are currently available, organizations should engage with the vendor for updates and apply them promptly once released. Additionally, reviewing and minimizing the attack surface by limiting unnecessary state-changing endpoints and enforcing strict referer header checks can further reduce risk.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-10-07T15:41:20.865Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695552dadb813ff03ef39014

Added to database: 12/31/2025, 4:44:10 PM

Last enriched: 1/20/2026, 10:26:00 PM

Last updated: 2/6/2026, 10:42:54 PM

Views: 44

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats