CVE-2025-67079
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 · uneditedFile upload vulnerability in Omnispace Agora Project before 25.10 allowing attackers to execute code through the MSL engine of the Imagick library via crafted PDF file to the file upload and thumbnail functions.
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 confidenceFile upload vulnerability in Omnispace Agora Project before version 25.10 allows attackers to upload crafted PDF files that trigger code execution through the Imagick library's MSL (Magick Scripting Language) engine via the thumbnail generation function.
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< 25.10CVSS 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.
-
Identify installed Agora Project versionLocate the Agora Project installation directory and check the version file, about page, or version constant. Common locations may include a version.php file, composer.json, or the application header/footer.Affected if The installed version is below 25.10 (e.g., 25.9, 25.8, older releases)
-
Confirm file upload functionality is enabledCheck the Agora Project configuration settings or admin panel for file upload options. Verify if the upload module is active and not disabled.Affected if File uploads are enabled and users can upload documents
-
Verify PDF upload capability existsInspect the allowed file type configuration in the upload handler. Check if PDF is included in the permitted MIME types or extensions.Affected if PDF files are accepted by the upload function
-
Check if Imagick library is installedRun phpinfo() or check the PHP extensions directory for the imagick extension. Alternatively, check if the system has the imagick binary installed.Affected if Imagick is installed and available to PHP
-
Confirm MSL processor is enabled in ImagickCheck the Imagick configuration file (typically imagick.ini or policy.xml) for MSL-related policy settings. Look for whether the MSL coder/processor is restricted or disabled.Affected if MSL (Magick Scripting Language) processor is not explicitly disabled in the Imagick configuration
You are affected if your Agora Project version is below 25.10 AND file uploads with PDF support are enabled AND Imagick with MSL processing is active on the server.
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 · scoped25.10
Disable or restrict the MSL processor in Imagick configuration, implement strict file type validation with magic byte checking on upload, and sanitize or reject PDF files containing embedded ImageMagick instructions.
25.10
- Upgrade Agora Project to version 25.10 or later
- Verify the upgrade was successful by checking the application version
- Review the official release notes for version 25.10 to confirm the MSL/Imagick vulnerability is addressed
- Test file upload functionality with standard PDF files to ensure normal operations work
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67079 — 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-67079 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