CVE-2025-29411: An arbitrary file upload vulnerability in the Client Profile Update section of Mart Developers iBanking v2.0.0

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2025-29411 is a critical-severity flaw (CVSS 9.8) affecting ibanking. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An arbitrary file upload vulnerability in the Client Profile Update section of Mart Developers iBanking v2.0.0 allows attackers to execute arbitrary code via uploading a crafted PHP file.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-434
Published	2025-03-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: martmbithi

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-20 15:15 UTCPublished CVE record published
2026-06-17 09:05 UTCUpdated Record last modified

martmbithi ibanking DOWNGRADE

Affected: 2.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy ibanking || rpm -q ibanking || ibanking --version

2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison ibanking sudo apt install ibanking=<VERSION_BEFORE_2.0.0> sudo apt-mark hold ibanking

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ibanking sudo dnf downgrade ibanking-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add ibanking

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-29411?

ibanking: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-29411 being exploited?

CVE-2025-29411 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-29411 affect?

CVE-2025-29411 affects ibanking. Severity is critical (CVSS 9.8). An arbitrary file upload vulnerability in the Client Profile Update section of Mart Developers iBanking v2.0.0 allows attackers to execute arbitrary code via uploading a crafted PHP file.

How urgent is CVE-2025-29411?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-29412 MEDIUM 4.8 DOWNGRADE A cross-site scripting (XSS) vulnerability in the Client Profile Update section of Mart Developers iBanking v2

References

← Back to latest CVEs