CVE-2010-4729

CVE-2010-4729 is a medium-severity vulnerability in Zikula Zikula Application Framework with a CVSS 2.0 base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

Zikula before 1.2.3 does not use the authid protection mechanism for (1) the lostpassword form and (2) mailpasswd processing, which makes it easier for remote attackers to generate a flood of password requests and possibly conduct cross-site request forgery (CSRF) attacks via multiple form submissions.

Frequently asked questions

What is CVE-2010-4729?
Zikula before 1.2.3 does not use the authid protection mechanism for (1) the lostpassword form and (2) mailpasswd processing, which makes it easier for remote attackers to generate a flood of password requests and possibly conduct cross-site request forgery (CSRF) attacks via multiple form submissions.
How severe is CVE-2010-4729?
CVE-2010-4729 has a CVSS 2.0 base score of 6.8, rated medium severity.
Is CVE-2010-4729 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-4729?
CVE-2010-4729 primarily affects Zikula Zikula Application Framework. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-4729?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-4729 published?
CVE-2010-4729 was published on 2011-02-08 and last updated on 2026-06-16.

References

Affected products (3)

More vulnerabilities in Zikula Zikula Application Framework

All CVEs affecting Zikula Zikula Application Framework →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →