CVE-2025-2244
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 · uneditedA vulnerability in the sendMailFromRemoteSource method in Emails.php as used in Bitdefender GravityZone Console unsafely uses php unserialize() on user-supplied input without validation. By crafting a malicious serialized payload, an attacker can trigger PHP object injection, perform a file write, and gain arbitrary command execution on the host system.
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 confidenceThe sendMailFromRemoteSource method in Bitdefender GravityZone Console's Emails.php unsafely uses PHP's unserialize() function on user-supplied input without validation. This allows attackers to craft malicious serialized PHP objects, achieve PHP object injection, write arbitrary files, and execute commands on the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.41.2-1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bitdefender GravityZone Console is installedLocate the GravityZone installation directory or check system services for GravityZone components. Common paths include /opt/gravityzone or C:\Program Files\Bitdefender\GravityZone on Linux/Windows respectively.Affected if The software is present on the system
-
Check the installed version numberUse the product's built-in version checker, or look for version metadata in the installation directory. Compare your version against the affected range: versions below 6.41.2-1 are vulnerable.Affected if The installed version is lower than 6.41.2-1
-
Locate the Emails.php fileSearch the GravityZone installation directory for the Emails.php file that contains the sendMailFromRemoteSource method. This file handles email-related functionality in the console.Affected if The Emails.php file exists in the installation directory
-
Inspect the vulnerable code patternOpen Emails.php and search for the sendMailFromRemoteSource method. Look for an unserialize() call operating on user-supplied or remote input without prior validation or sanitization.Affected if The unserialize() call exists in the sendMailFromRemoteSource method and processes untrusted input without validation
The environment is affected if Bitdefender GravityZone Console is installed with a version lower than 6.41.2-1 and the Emails.php file contains the vulnerable unserialize() pattern in the sendMailFromRemoteSource method.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.41.2-1
Replace unsafe unserialize() calls with safer alternatives such as json_decode() or implement strict input validation and whitelisting. Apply vendor patches immediately as this is a critical remote code execution vulnerability.
GravityZone version 6.41.2-1 or later
- Upgrade Bitdefender GravityZone Console to version 6.41.2-1 or later
- Verify the upgrade was successful by checking the installed version in the console
- Confirm the Emails.php file has been updated and no longer contains the unsafe unserialize() call
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2244 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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