CVE-2007-5148
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in FrontAccounting (FA) 1.12 allow remote attackers to execute arbitrary PHP code via a URL in the path_to_root parameter to (1) access/logout.php or certain PHP scripts under (2) admin/, (3) dimensions/, (4) gl/, (5) inventory/, (6) manufacturing/, (7) purchasing/, (8) reporting/, (9) sales/, or (10) taxes/. NOTE: the config.php vector is already covered by CVE-2007-4279, and the login.php and language.php vectors are already covered by CVE-2007-5117. NOTE: this issue is disputed by CVE because path_to_root is defined before use in all of the other files reported in the original disclosure
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 confidenceRemote File Inclusion vulnerability in FrontAccounting 1.12 allows arbitrary PHP code execution via URL in the path_to_root parameter to multiple PHP scripts under admin/, dimensions/, gl/, inventory/, manufacturing/, purchasing/, reporting/, sales/, and taxes/ directories, plus access/logout.php. However, the CVE is disputed as the description notes path_to_root is defined before use in the reported files, potentially mitigating exploitation.
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= 1.12CVSS 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 FrontAccounting versionLocate the version file or header in the FrontAccounting installation (commonly in includes/version.php or a VERSION file in the root directory)Affected if The installed version is exactly 1.12 (version 1.12)
-
Verify path_to_root definition in vulnerable scriptsOpen one of the reported PHP scripts (e.g., admin/users.php, sales/index.php) and examine whether the $path_to_root variable is defined/assigned BEFORE any include or require statements that use itAffected if The $path_to_root variable is NOT defined before inclusion operations, allowing user-controlled input to be used in include/require statements
-
Check if path_to_root can be user-controlledExamine the PHP scripts to determine if the path_to_root parameter is taken directly from user input (GET/POST request) without validation or sanitizationAffected if The path_to_root parameter is directly used from user input without being hardcoded or validated against a whitelist of allowed values
-
Test for actual RFI susceptibilityIf you have a test environment, attempt a benign inclusion by passing a non-existent local path to path_to_root parameter to one of the affected scripts and observe if the application attempts to include itAffected if The application attempts to include the provided path, indicating the parameter is not properly validated before use
-
Review application configuration for hardcoded pathsCheck the application configuration files (e.g., config.php) to see if path_to_root is hardcoded to a fixed value rather than derived from user inputAffected if path_to_root is not hardcoded and instead relies on user-supplied values in the request
You are affected only if you are running FrontAccounting version 1.12 AND the path_to_root parameter is not defined/hardcoded before inclusion operations, allowing external input to control which file is included.
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 dataEnsure path_to_root parameter cannot be user-controlled or upgrade to a patched version of FrontAccounting; verify that path_to_root is defined/validated before inclusion operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5148 — 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-5148 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