Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-4609: REDCap before 5.0.4 and 5.1.x before 5.1.3 does not reject certain undocumented syntax within branching logic

41
This month
MEDIUM 6.5DOWNGRADEUPGRADE

CVE-2013-4609 is a medium-severity flaw (CVSS 6.5) affecting redcap, redcap. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

REDCap before 5.0.4 and 5.1.x before 5.1.3 does not reject certain undocumented syntax within branching logic and calculations, which allows remote authenticated users to bypass intended access restrictions via (1) the Online Designer or (2) the Data Dictionary upload, as demonstrated by an eval call.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
EPSS exploit chance1.5% (top 26%)
CISA exploited listNo
WeaknessCWE-264
Published2013-06-17
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: project-redcap · vanderbilt

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

project-redcap redcap DOWNGRADE
Affected: 4.13.18 · 4.14.5 · 4.14.6 · 4.15.0 · 4.15.1 · 4.15.2 · 4.15.3 · 4.15.4
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.13.18
1. Check installed version
apt-cache policy redcap || rpm -q redcap || redcap --version
2. No fixed release: DOWNGRADE to a release before 4.13.18 (Debian / Ubuntu)
apt-cache madison redcap sudo apt install redcap=<VERSION_BEFORE_4.13.18> sudo apt-mark hold redcap
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list redcap sudo dnf downgrade redcap-<VERSION_BEFORE_4.13.18> sudo dnf versionlock add redcap
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.
vanderbilt redcap UPGRADE
Affected: <= 5.0.3 · 4.14.0 · 4.14.1 · 4.14.2 · 4.14.3 · 4.14.4
Fixed in: newer than 5.0.3
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy redcap || rpm -q redcap || redcap --version
2. UPGRADE to newer than 5.0.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade redcap
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade redcap
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
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-2013-4609?

redcap: downgrade or apply the listed mitigation; redcap: upgrade to newer than 5.0.3. Exact commands for each OS are on this page.

Is CVE-2013-4609 being exploited?

CVE-2013-4609 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-2013-4609 affect?

CVE-2013-4609 affects redcap, redcap. Severity is medium (CVSS 6.5). REDCap before 5.0.4 and 5.1.x before 5.1.3 does not reject certain undocumented syntax within branching logic and calculations, which allows remote authenticated users to bypass intended access restrictions via (1) the Online Designer or (2

How urgent is CVE-2013-4609?

Priority 41/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.