CVE-2025-44658
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 · uneditedIn Netgear RAX30 V1.0.10.94, a PHP-FPM misconfiguration vulnerability is caused by not following the specification to only limit FPM to .php extensions. An attacker may exploit this by uploading malicious scripts disguised with alternate extensions and tricking the web server into executing them as PHP, bypassing security mechanisms based on file extension filtering. This may lead to remote code execution (RCE), information disclosure, or full system compromise.
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 confidenceThe Netgear RAX30 router firmware V1.0.10.94 contains a PHP-FPM misconfiguration where the FastCGI Process Manager is not restricted to executing only files with .php extensions. This allows attackers to upload malicious scripts with alternate extensions (such as .php3, .php5, or other file types) that the web server will still execute as PHP code, bypassing extension-based security filters.
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.0.10.94CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Confirm router model and firmware versionAccess the router admin web interface (typically at 192.168.1.1) and navigate to Settings > Firmware Version or check the bottom of the router for the model number. Alternatively, check via CLI if you have telnet/SSH access.Affected if The device is a Netgear RAX30 running firmware version 1.0.10.94 specifically.
-
Access PHP-FPM configurationIf you have shell access to the router (via telnet, SSH, or serial console), locate the PHP-FPM configuration file, typically found in /etc/php-fpm.conf, /etc/php/*/php-fpm.conf, or within the web server configuration directory.Affected if The PHP-FPM configuration file exists and can be inspected.
-
Check for security.limit_extensions directiveExamine the PHP-FPM pool configuration for the security.limit_extensions setting. This directive should be present and explicitly set to only allow .php files (e.g., security.limit_extensions = .php).Affected if The security.limit_extensions directive is missing, commented out, or includes extensions other than .php (such as .php3, .php5, .phtml).
-
Inspect web server PHP handler configurationCheck the web server configuration (nginx, lighttpd, or apache depending on firmware) for PHP handler mappings. Look for fastcgi_pass or PHP execution rules that may accept multiple file extensions.Affected if The web server is configured to execute PHP files based on extensions other than .php, or PHP-FPM is not validating file extensions before execution.
-
Review uploaded files on the deviceIf the router has any file upload functionality (for logs, backups, or themes), examine the storage directories (commonly /www, /var/www, /tmp, or USB storage if applicable) for files with .php3, .php5, .phtml, or other executable extensions.Affected if Any non-standard PHP extension files exist in web-accessible directories that could be executed as PHP code.
The device is affected if it is a Netgear RAX30 running firmware 1.0.10.94 and the PHP-FPM security.limit_extensions directive is not properly configured to restrict execution to only .php files.
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.
dbcve · scopedThe vendor should release a firmware update that properly configures PHP-FPM to only process .php files. Users should update to the patched firmware version once available and disable any unused file upload features until the update is applied.
Netgear RAX30 firmware version newer than 1.0.10.94 (check Netgear support for latest stable release)
- 1. Visit the official Netgear support website at www.netgear.com/support/
- 2. Search for the RAX30 router model and check for available firmware updates
- 3. Download the latest firmware version newer than 1.0.10.94
- 4. Access the router's web management interface (typically at 192.168.1.1)
- 5. Navigate to the Administration or Firmware Update section
- 6. Upload and apply the new firmware version
- 7. After the router reboots, verify the firmware version has been updated
- 8. As a secondary mitigation, if you have access to the underlying system, ensure PHP-FPM is configured to only process .php extensions by reviewing the fpm configuration files and restricting file type handling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-44658 — 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-44658 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