dbcve.org
MaseApplication · Bibtex

CVE-2007-2260

HIGH · 7.5 CVSS v2.0 Published 2007-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Multiple PHP remote file inclusion vulnerabilities in bibtex mase beta 2.0 allow remote attackers to execute arbitrary PHP code via a URL in the bibtexrootrel parameter to (1) unavailable.php, (2) source.php, (3) log.php, (4) latex.php, (5) indexinfo.php, (6) index.php, (7) importinfo.php, (8) import.php, (9) examplefile.php, (10) clearinfo.php, (11) clear.php, (12) aboutinfo.php, (13) about.php, and other unspecified files.

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 confidence

Remote file inclusion vulnerability in bibtex mase beta 2.0 allows execution of arbitrary PHP code via the bibtexrootrel parameter in multiple PHP files (unavailable.php, source.php, log.php, latex.php, indexinfo.php, index.php, importinfo.php, import.php, examplefile.php, clearinfo.php, clear.php, aboutinfo.php, about.php). Attackers can inject a remote URL containing malicious PHP code that gets included and executed by the vulnerable application.

MitigationDisable PHP's allow_url_include setting in php.ini, upgrade to a patched version of bibtex mase if available, or implement strict input validation on the bibtexrootrel parameter to prevent URL injection. As a temporary measure, consider restricting access to the affected application until patched.

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
MaseApplication
Affected:= 2.0_beta

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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

  1. Identify if Bibtex Mase is installed
    Search the web server document root for the bibtex mase application directory or files named after the product (search for 'bibtex' in directory names or check for typical installation paths like /bibtex, /bibtex-mase, or search for characteristic PHP files from the affected list)
    Affected if The application is found on the server and appears to be Bibtex Mase
  2. Check the installed version
    Locate any version file, readme, or header comments in the main PHP files that may indicate the version. Common locations include version.php, README files, or the index.php header
    Affected if The version is 2.0_beta exactly
  3. Verify vulnerable PHP files exist
    Check for the presence of the affected PHP files in the web directory: unavailable.php, source.php, log.php, latex.php, indexinfo.php, index.php, importinfo.php, import.php, examplefile.php, clearinfo.php, clear.php, aboutinfo.php, about.php
    Affected if Any of these files exist in the web-accessible directory
  4. Check PHP configuration for URL inclusion
    Create a phpinfo page or check php.ini for the allow_url_include setting (also check allow_url_fopen). This can be done by creating a temporary PHP file with 'phpinfo();' or checking the server configuration
    Affected if allow_url_include is set to On (enabled)
  5. Test bibtexrootrel parameter accessibility
    Attempt a controlled test by making a request to one of the affected PHP files with a benign test value for bibtexrootrel (e.g., ?bibtexrootrel=test) and observe if the application attempts to include it as a file path
    Affected if The application accepts and processes the bibtexrootrel parameter without sanitization, allowing external URL injection

You are affected if Bibtex Mase 2.0_beta is installed, the vulnerable PHP files are present, and PHP's allow_url_include setting is enabled, allowing remote file inclusion via the bibtexrootrel parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable PHP's allow_url_include setting in php.ini, upgrade to a patched version of bibtex mase if available, or implement strict input validation on the bibtexrootrel parameter to prevent URL injection. As a temporary measure, consider restricting access to the affected application until patched.

Fix this in Mase Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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