CVE-2025-9461
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 weakness has been identified in diyhi bbs up to 6.8. The impacted element is an unknown function of the file src/main/java/cms/web/action/filePackage/FilePackageManageAction.java of the component File Compression Handler. This manipulation of the argument idGroup causes information disclosure. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited.
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 confidenceDIYHI BBS versions up to 6.8 contain an information disclosure vulnerability in the FilePackageManageAction.java file within the File Compression Handler component. The idGroup parameter is not properly validated, allowing unauthorized users to access sensitive file package information without authentication.
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.8CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify installed DIYHI BBS versionCheck the application version from the web interface (typically in footer, about page, or admin panel) or check version file in the installation directoryAffected if Version is 6.8 or lower (any version up to and including 6.8)
-
Confirm File Compression Handler component is presentLocate FilePackageManageAction.java in the application installation, typically under src/com/file/ or similar path within the webapp structureAffected if The FilePackageManageAction.java file exists in the application deployment
-
Verify the vulnerable endpoint is accessible without authenticationAccess the file package management endpoint - typically at a URL path containing 'FilePackageManage' or related file handling actions (e.g., /file/packageManage or /action/FilePackageManageAction) - without providing any login credentialsAffected if The endpoint returns a valid response (rather than an authentication error or redirect to login) when accessed without credentials
-
Test idGroup parameter exposureSend a crafted HTTP request to the file package management endpoint with an arbitrary idGroup parameter value (e.g., ?idGroup=1 or ?idGroup=test) without authenticationAffected if The response contains file package information, file paths, or sensitive data related to the idGroup value without requiring authorization
The environment is affected if running DIYHI BBS version 6.8 or lower AND the File Compression Handler component is exposed without requiring authentication, allowing the idGroup parameter to leak sensitive file package information.
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.
From vendor dataImplement proper authorization checks and access controls on the file package management endpoints to validate user permissions before returning any file package information associated with the idGroup parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9461 — 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-9461 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