CVE-2015-7317: Kupu 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, and 4.2.0 through 4.2.7 allows remote aut

This month

MEDIUM 6.8UPGRADEDOWNGRADE

CVE-2015-7317 is a medium-severity flaw (CVSS 6.8) affecting kupu, plone. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Kupu 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, and 4.2.0 through 4.2.7 allows remote authenticated users to edit Kupu settings.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.8 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.9% (top 21%)
CISA exploited list	No
Weakness	CWE-264
Published	2017-09-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: kupu project · plone

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

Am I affected?

Timeline

2017-09-25 17:29 UTCPublished CVE record published
2026-06-17 00:32 UTCUpdated Record last modified

kupu project kupu UPGRADE

Affected: <= 1.4.16

Fixed in: newer than 1.4.16

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.4.16 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kupu

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kupu

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

plone plone DOWNGRADE

Affected: 3.3 · 3.3.1 · 3.3.2 · 3.3.3 · 3.3.4 · 3.3.5 · 3.3.6 · 4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.3

1. Check installed version

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

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

apt-cache madison plone sudo apt install plone=<VERSION_BEFORE_3.3> sudo apt-mark hold plone

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

dnf --showduplicates list plone sudo dnf downgrade plone-<VERSION_BEFORE_3.3> sudo dnf versionlock add plone

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-2015-7317?

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

Is CVE-2015-7317 being exploited?

CVE-2015-7317 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-2015-7317 affect?

CVE-2015-7317 affects kupu, plone. Severity is medium (CVSS 6.8). Kupu 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, and 4.2.0 through 4.2.7 allows remote authenticated users to edit Kupu settings.

How urgent is CVE-2015-7317?

Priority 44/100. No elevated risk signals yet.

References

← Back to latest CVEs