dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-2376

HIGH · 7.3 CVSS v3.1 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in viames Pair Framework up to 1.9.11 and classified as critical. Affected by this vulnerability is the function getCookieContent of the file /src/UserRemember.php of the component PHP Object Handler. The manipulation of the argument cookieName leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PHP Object Injection in viames Pair Framework's UserRemember.php component. The getCookieContent function deserializes user-controlled input from the cookieName parameter without proper sanitization, allowing remote attackers to inject arbitrary PHP objects and potentially achieve remote code execution.

MitigationUpgrade to version 1.9.12 or later. If upgrading is not immediately feasible, implement strict input validation on the cookieName parameter before deserialization, or replace PHP's unserialize() with a safer alternative like JSON encoding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the viames Pair Framework installation
    Search for the Pair Framework codebase on your server. Look for directories containing 'pair' or 'viames' in the path, or check your web application's dependency manager (e.g., composer.json) for the viames/pair package.
    Affected if The viames Pair Framework is present in your environment.
  2. Identify the installed version
    Check the version of the viames Pair Framework. If using Composer, run 'composer show viames/pair' or inspect your composer.lock file. Otherwise, look for a version file or tag within the framework directory.
    Affected if The installed version is earlier than 1.9.12.
  3. Locate UserRemember.php
    Find the UserRemember.php file within the Pair Framework directory structure. This file typically resides in an authentication or session-related path.
    Affected if The UserRemember.php file exists in your installation.
  4. Examine the getCookieContent function
    Open UserRemember.php and locate the getCookieContent function. Verify if it contains a call to PHP's unserialize() function that processes input from the cookieName parameter without prior validation.
    Affected if The function uses unserialize() on the cookieName parameter without sanitization.
  5. Confirm cookie-based authentication is in use
    Check your application's configuration and codebase to determine if the Remember Me or user persistence feature provided by UserRemember is enabled. Look for cookie settings related to user authentication.
    Affected if Cookie-based user remember functionality is enabled and in use.

You are affected if the viames Pair Framework version is below 1.9.12 AND the UserRemember.php component with its vulnerable getCookieContent function is present and active in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.9.12 or later. If upgrading is not immediately feasible, implement strict input validation on the cookieName parameter before deserialization, or replace PHP's unserialize() with a safer alternative like JSON encoding.

Recommended fix Moderate confidence

1.9.12 or later

  1. 1. Identify the current version of viames Pair Framework in use by checking composer.json or the framework's version file
  2. 2. If the version is 1.9.11 or below, plan an upgrade to the latest stable release
  3. 3. Update the composer.json dependency to require a version higher than 1.9.11 (e.g., composer require viames/pair-framework:^1.9.12 or the latest available version)
  4. 4. Run composer update to apply the changes
  5. 5. Test the application thoroughly, specifically the UserRemember.php component and cookie handling functionality
  6. 6. Verify the getCookieContent function no longer accepts unsanitized input for the cookieName parameter

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2376 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data