dbcve.org
Agora ProjectApplication

CVE-2025-67077

HIGH · 8.8 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 25.10 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
File upload vulnerability in Omnispace Agora Project before 25.10 allowing authenticated, or under certain conditions also guest users, via the UploadTmpFile action.

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

Omnispace Agora Project versions before 25.10 contain a file upload vulnerability in the UploadTmpFile action that allows authenticated users to upload files, with certain conditions also permitting guest users to exploit this. The vulnerability enables unauthorized file upload which could lead to remote code execution if malicious files are stored and subsequently accessed.

MitigationRestrict file upload functionality to properly authenticated users only, implement strict file type validation and content inspection, store uploads outside web root with randomized filenames, and upgrade to version 25.10 or later.

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
Agora ProjectApplication
Affected:< 25.10

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Determine installed Agora Project version
    Locate the version file or admin panel that displays the current Agora Project version number
    Affected if The installed version is below 25.10
  2. Identify if UploadTmpFile action is exposed
    Check web server logs or application routing configuration for requests to the UploadTmpFile endpoint/action
    Affected if The UploadTmpFile action is accessible and responds to requests
  3. Verify upload functionality authentication settings
    Examine the application configuration or user role permissions to determine if guest/unauthenticated users can access the file upload feature
    Affected if Guest users are permitted to access file upload functionality or if the authentication check is missing/disabled for UploadTmpFile
  4. Inspect uploaded file storage location
    Review the file storage configuration to determine if uploaded files are stored within the web root directory
    Affected if Uploaded files are stored in a location accessible via web browser without additional access controls
  5. Check for unexpected file types in upload directory
    List files in the designated upload directory and verify if executable or script-based files (php, asp, jsp, etc.) are present
    Affected if Executable or script files exist in the upload directory that were not intentionally placed there by administrators

A user is affected if their Agora Project installation is version below 25.10 AND the UploadTmpFile action is accessible, particularly to guest users or without proper file type 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.

dbcve · scoped
Upgrade available Upgrade to 25.10 or later
Fixed in 25.10
Interim mitigation

Restrict file upload functionality to properly authenticated users only, implement strict file type validation and content inspection, store uploads outside web root with randomized filenames, and upgrade to version 25.10 or later.

Recommended fix High confidence

25.10

  1. 1. Back up the current Agora Project installation and database before proceeding
  2. 2. Download the latest Agora Project version 25.10 or later from the official source (www.agora-project.net)
  3. 3. Replace the existing application files with the new version 25.10 files
  4. 4. Verify that the UploadTmpFile action is properly handled in the new version
  5. 5. Test the file upload functionality to confirm the vulnerability is remediated
  6. 6. If guest access is enabled, verify that the upload restrictions are properly enforced
  7. 7. Monitor for any unexpected behavior after the upgrade

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

Fix this in Agora Project Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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