CVE-2007-1789
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 · uneditedFlyspray 0.9.9 allows remote attackers to obtain sensitive information (private project summaries) via direct requests.
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 confidenceFlyspray 0.9.9 contains an information disclosure vulnerability where the application fails to properly enforce access controls on private project summaries. Remote attackers can obtain sensitive information by making direct requests to specific URLs or endpoints that expose private project data without authentication or authorization verification.
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= 0.9.9CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Flyspray versionLocate the version file or footer on the Flyspray installation, typically found in the index page source, about page, or version configuration fileAffected if The installed version is exactly 0.9.9
-
Verify private projects existLog into the Flyspray admin panel and check if any projects have visibility set to private or restrictedAffected if Private or restricted-access projects are configured in the system
-
Test unauthenticated access to project endpointsAttempt to access common project-related URLs without authentication, such as /index.php?do=details&task_id=1 or /project/1 summaries, using a browser or curl in an unauthenticated sessionAffected if Private project details or summaries are returned without requiring login credentials
-
Inspect HTTP response behaviorSend a request to project summary endpoints and examine whether the application returns HTTP 200 with project data or redirects to a login page (HTTP 302)Affected if The application returns project data (HTTP 200) instead of redirecting to authentication for private projects
-
Review access control configurationCheck the Flyspray configuration files and database for permission settings related to project visibility and ensure role-based access controls are properly enforcedAffected if No authentication or authorization check is performed before displaying private project information
A user is affected if running Flyspray version 0.9.9 and the application exposes private project summaries or details to unauthenticated users via direct URL access.
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 authentication and session validation along with role-based access control (RBAC) checks to ensure private project summaries are only accessible to authenticated users with appropriate permissions.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1789 — 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-2007-1789 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