CVE-2025-12549
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in magentech Rozy - Flower Shop rozy allows PHP Local File Inclusion.This issue affects Rozy - Flower Shop: from n/a through <= 1.2.25.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the magentech Rozy - Flower Shop e-commerce template (versions <= 1.2.25). The vulnerability stems from improper control of filename parameters used in PHP include/require statements, allowing attackers to manipulate file paths to read sensitive server files. With CVSS 8.1 (HIGH), this can expose configuration files, credentials, and potentially lead to remote code execution depending on server configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the Rozy template versionLocate the version definition file in the template directory (typically version.php, config.php, or similar in the template root). Open the file and read the version constant or variable.Affected if The version number returned is 1.2.25 or lower.
-
Find PHP files using dynamic file includesSearch the template's PHP files for include, require, include_once, or require_once statements that use variables or parameters in the file path (e.g., include($file), include($_GET['page']). Identify the specific file and line numbers.Affected if Dynamic file inclusion using user-supplied input is found in the codebase.
-
Verify the vulnerable parameter is reachableExamine the identified include/require code path to determine if the variable originates from HTTP request parameters (GET, POST, COOKIE). Test by attempting to access the page with a modified parameter.Affected if User-controlled input reaches the file inclusion function without sanitization.
-
Test for path traversal capabilityAttempt to access the vulnerable endpoint with a path traversal payload (e.g., ../../../../etc/passwd) in the parameter. Observe if the server returns file contents or an error revealing the file path.Affected if The application returns content from files outside the intended directory or displays the full path.
You are affected if the Rozy template version is 1.2.25 or lower AND your installation contains PHP code that dynamically includes files using unsanitized user input from HTTP parameters.
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 strict input validation using whitelist-based file inclusion, apply basename() and realpath() functions to sanitize path traversal attempts, and disable allow_url_include. Alternatively, refactor to use a switch/case or array-based include mechanism that does not rely on user-supplied input for file paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12549 — 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-12549 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