CVE-2007-2265
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 YA Book 0.98-alpha allows remote attackers to inject arbitrary web script or HTML via the City field in a sign action in index.php.
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 confidenceYA Book 0.98-alpha contains a reflected cross-site scripting (XSS) vulnerability in the City field of the guestbook sign-in functionality in index.php. User-supplied input in the City parameter is rendered without proper sanitization or output encoding, allowing injection of arbitrary HTML or script tags.
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.98_alphaCVSS 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 if Phpee Ya Book is installedSearch for index.php files that contain 'guestbook' or 'Ya Book' references in your web root directories. Common paths may include /yabook/, /guestbook/, or the root web directory.Affected if Phpee Ya Book software is present on the server
-
Verify the installed version is 0.98_alphaLocate version information in the application - check for version files, readme.txt, or the header sections of PHP files that may contain version strings like '0.98' or 'alpha'.Affected if The installed version is exactly 0.98_alpha
-
Confirm the vulnerable City field existsExamine index.php for the guestbook sign-in functionality and locate the City input field processing. Look for form handling code that accepts and processes the City parameter without visible sanitization.Affected if The index.php file contains guestbook sign-in code with a City input field that accepts user-supplied data
-
Check if the guestbook feature is enabledDetermine whether the guestbook functionality is active and accessible. This may involve checking configuration files or confirming the sign-in form is publicly reachable.Affected if The guestbook sign-in form with the City field is accessible and operational
A user is affected if Phpee Ya Book version 0.98_alpha is installed and the guestbook sign-in functionality with the City field is enabled and accessible.
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 dataApply input validation on the City field combined with proper output encoding when displaying user-submitted content. Alternatively, implement a content security policy (CSP) to mitigate XSS execution.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2265 — 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-2265 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