CVE-2025-67078
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 · uneditedCross site scripting (XSS) vulnerability in Omnispace Agora Project before 25.10 allowing attackers to execute arbitrary code via the notify parameter of the file controller used to display errors.
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 confidenceA reflected XSS vulnerability in the file controller of Omnispace Agora Project versions before 25.10 allows attackers to inject arbitrary JavaScript code through the notify parameter when the application displays error messages.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Omnispace Agora Project is installedLocate the Agora Project installation directory or identify the running web application serving Agora Project contentAffected if The software is present in the environment
-
Determine installed versionCheck the version number of the Agora Project installation (typically visible in admin interface, version file, or about page)Affected if Version is below 25.10 (e.g., 25.09, 25.08, earlier releases)
-
Verify file controller is accessibleConfirm the file controller endpoint is reachable via HTTP/HTTPS on the web server hosting Agora ProjectAffected if The file controller responds to requests and can display error messages
-
Test notify parameter in error contextSubmit a request to the file controller with a crafted notify parameter containing a test payload (e.g., <script>alert(1)</script>) to trigger an error message, then inspect if the payload is reflected unencoded in the responseAffected if The notify parameter value appears verbatim in the error output without HTML encoding
A user is affected if Agora Project version is below 25.10 AND the file controller is accessible and reflects the notify parameter unencoded in error messages.
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
Implement strict input validation and proper output encoding on the notify parameter in the file controller error display logic; upgrade to version 25.10 or later which contains the patch.
25.10
- 1. Back up the current Agora Project installation and database before proceeding with any upgrade.
- 2. Download Agora Project version 25.10 or later from the official source (www.agora-project.net or www.helx.io).
- 3. Review any upgrade documentation provided with the release for version 25.10.
- 4. Replace the existing Agora Project files with the new version 25.10 files.
- 5. Verify the upgrade was successful by accessing the application.
- 6. Test that the file controller's notify parameter is properly sanitized and the XSS vulnerability is no longer present.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-67078 — 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-67078 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