dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-11135

HIGH · 7.3 CVSS v3.1 Published 2025-09-29
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 was detected in pmTicket Project-Management-Software up to 2ef379da2075f4761a2c9029cf91d073474e7486. The affected element is the function loadLanguage of the file classes/class.database.php of the component Cookie Handler. Performing manipulation of the argument user_id results in deserialization. The attack can be initiated remotely. The exploit is now public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

This is an insecure deserialization vulnerability in pmTicket's Cookie Handler component. The loadLanguage function in classes/class.database.php uses PHP's unserialize() on the user_id parameter from cookies without proper validation, allowing remote attackers to inject malicious serialized objects. The vulnerability is exploitable remotely and a public exploit exists.

MitigationReplace PHP unserialize() with safer alternatives like JSON encoding/decoding, or implement strict input validation and allowlist filtering before deserialization. Additionally, consider implementing cryptographic signatures on cookie values to prevent tampering.

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 pmTicket installation
    Search for the pmTicket application directory on the server, typically found in web root directories. Look for directories containing 'pmticket' or check known web application paths.
    Affected if pmTicket is installed on the server
  2. Identify pmTicket version
    Check for version files or headers within the pmTicket installation. Common locations include a VERSION file, version in an installer script, or within PHP files that define version constants.
    Affected if Unable to determine version or version is unknown
  3. Verify vulnerable file exists
    Locate the file classes/class.database.php within the pmTicket installation directory.
    Affected if The file classes/class.database.php exists in the pmTicket installation
  4. Confirm vulnerable unserialize call
    Examine the loadLanguage function in classes/class.database.php. Search for code that calls unserialize() on $_COOKIE['user_id'] or similar cookie parameters without validation.
    Affected if The loadLanguage function contains unserialize() calls on cookie data without input validation
  5. Verify cookie-based authentication is active
    Check if the application uses cookies for user session handling and if the user_id cookie parameter is processed by the application.
    Affected if The application processes user_id from cookies and uses it in deserialization operations

A system is affected if pmTicket is installed and the loadLanguage function in classes/class.database.php uses unserialize() on cookie values (specifically user_id) without validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace PHP unserialize() with safer alternatives like JSON encoding/decoding, or implement strict input validation and allowlist filtering before deserialization. Additionally, consider implementing cryptographic signatures on cookie values to prevent tampering.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11135 — 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-11135 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