CVE-2025-30582
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in aytechnet DyaPress ERP/CRM dyapress allows PHP Local File Inclusion.This issue affects DyaPress ERP/CRM: from n/a through <= 18.0.2.0.
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 confidencePath traversal vulnerability in DyaPress ERP/CRM allows attackers to use directory traversal sequences (../) in user-supplied input to access files outside restricted directories, combined with PHP local file inclusion enabling potential arbitrary code execution or sensitive file disclosure.
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 DyaPress ERP/CRM installationSearch for DyaPress installation directories (common paths: /var/www/html/dyapress, /home/*/public_html/dyapress, C:\inetpub\wwwroot\dyapress) or look for dyapress-specific configuration files and databasesAffected if DyaPress ERP/CRM is installed on the system
-
Determine DyaPress versionCheck version file (typically version.php, about.php, or config files in the root directory) or access the admin dashboard About sectionAffected if Version cannot be determined or is older than any publicly available patch
-
Identify file inclusion endpointsSearch web directory for PHP files using include, require, include_once, or require_once with variable parameters (e.g., grep -r 'include($' /path/to/dyapress). Common vulnerable patterns: include($_GET['page']), require($_POST['file'])Affected if PHP files accept user-controlled input for file inclusion without sanitization
-
Verify directory traversal is possibleTest suspected endpoints with traversal sequences (e.g., ../../../../etc/passwd) in vulnerable parameters. Check if input validation blocks or allows ../ sequencesAffected if Directory traversal sequences are not blocked and file contents outside the webroot can be retrieved
-
Check PHP configuration for file inclusion risksExamine php.ini for allow_url_fopen=On and allow_url_include=On settings. These increase exploitation severity but are not required for the traversal itselfAffected if allow_url_include is enabled, allowing remote file inclusion in addition to local file inclusion
The environment is affected if DyaPress ERP/CRM is installed with accessible file inclusion functionality that does not sanitize directory traversal sequences from user input.
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 with allowlist-based path sanitization, restrict file inclusion to whitelisted directories, and upgrade to a patched version if available.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30582 — 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-30582 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