dbcve.org
E107Application

CVE-2025-61505

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to after 2.3.3 or later.
See remediation →
74/100
Remediation priority · Elevated
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
e107 CMS thru 2.3.3 are vulnerable to insecure deserialization in the `install.php` script. The script processes user-controlled input in the `previous_steps` POST parameter using `unserialize(base64_decode())` without validation, allowing attackers to craft malicious serialized data. This could lead to remote code execution, arbitrary file operations, or denial of service, depending on available PHP object gadgets in the codebase.

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

e107 CMS versions 2.3.3 and prior contain an insecure deserialization vulnerability in the install.php script. The script directly unserializes user-controlled input from the POST parameter 'previous_steps' after base64 decoding, without any validation or sanitization. This allows attackers to inject malicious PHP serialized objects that could trigger gadget chains for remote code execution, file operations, or denial of service.

MitigationReplace the insecure `unserialize(base64_decode())` calls on user input with safer alternatives such as JSON decoding, or implement strict allowlist validation if deserialization is absolutely required. Additionally, restrict or disable the install.php script in production environments.

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
E107Application
Affected:<= 2.3.3

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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. Confirm e107 CMS installation
    Locate e107 CMS files on the server - look for the main index.php file or e107.class.php in the web root. Check for the presence of the install.php script in the same directory.
    Affected if e107 CMS is installed and the install.php script exists on the server.
  2. Identify installed e107 version
    Check the version file or header. Common locations include a version.php file, e107.class.php, or the admin area. Look for a version declaration or meta tag showing the version number.
    Affected if The installed version is 2.3.3 or any version prior to 2.3.3.
  3. Verify install.php is accessible
    Attempt to access install.php via HTTP/HTTPS request from the web root. Check if the script responds or returns the installation page.
    Affected if The install.php script is accessible over the network in a production environment.
  4. Inspect install.php for vulnerable code pattern
    Open install.php in a code editor or via command line. Search for the pattern: unserialize(base64_decode( particularly looking for $_POST['previous_steps'] being passed to base64_decode and then unserialize.
    Affected if The install.php script contains unserialize(base64_decode($_POST['previous_steps'])) or similar insecure deserialization of user input without validation.

The environment is affected if e107 CMS version 2.3.3 or lower is installed AND the install.php script is accessible AND it contains the insecure unserialize call on the POST parameter 'previous_steps'.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.3
Interim mitigation

Replace the insecure `unserialize(base64_decode())` calls on user input with safer alternatives such as JSON decoding, or implement strict allowlist validation if deserialization is absolutely required. Additionally, restrict or disable the install.php script in production environments.

Recommended fix Moderate confidence

e107 CMS 2.4.0 or latest stable release

  1. 1. Back up the entire e107 CMS installation and database before making any changes.
  2. 2. Navigate to the official e107 CMS repository or download page at e107.org.
  3. 3. Download the latest stable version of e107 CMS (version 2.4.0 or higher if available).
  4. 4. Replace the existing installation files with the new version, preserving custom content, themes, and plugins in the /e107_themes/ and /e107_plugins/ directories.
  5. 5. Review and restore any custom configurations in e107.php or other configuration files.
  6. 6. Verify the /install.php script has been updated or removed in the new version.
  7. 7. Test the application functionality to ensure the upgrade was successful.
  8. 8. If the upgrade is not immediately possible, remove or rename the install.php file from the server to prevent exploitation.
Caveat Minor breaking changes may occur between major versions; review release notes for deprecated features or database schema changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in E107 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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