Skip to content
Noroxi
CVE-2017-1000481· NVD / CVE Program· CNA mitre

When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' parameter set to the previous

When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' parameter set to the previous url. After you login, you get redirected to the page you tried to view before. An attacker might try to abuse this by letting you click on a specially crafted link. You would login, and get redirected to the site of the attacker, letting you think that you are still on the original Plone site. Or some javascript of the attacker could be executed. Most of these types of attacks are already blocked by Plone, using the `isURLInPortal` check to make sure we only redirect to a page on the same Plone site. But a few more ways of tricking Plone into accepting a malicious link were discovered, and fixed with this hotfix.

MediumCVSS 6.1 · v3.0—No exploit Fix available
Published
Jan 3, 2018
Updated
Jun 16, 2026
EPSS
0.7% · 51th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

Affected systems

VendorProduct
ploneplone

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • plone plone2.5.5
  • plone plone3.3
  • plone plone3.3.1
  • plone plone3.3.2
  • plone plone3.3.3
  • plone plone3.3.4
  • plone plone3.3.5
  • plone plone3.3.6
  • plone plone4.0
  • plone plone4.0.1
  • plone plone4.0.10
  • plone plone4.0.2
  • plone plone4.0.3
  • plone plone4.0.4
  • plone plone4.0.5
  • plone plone4.0.7
  • plone plone4.0.8
  • plone plone4.0.9
  • plone plone4.1
  • plone plone4.1.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIplonefrom 2.5 · before 4.3.164.3.16
PyPIplonefrom 5 · before 5.1.05.1.0
PyPIproducts-cmfplonefrom 5.0.0 · before 5.0.105.0.10
PyPIproducts-cmfplonefrom 5.1a1 · before 5.1.05.1.0
PyPIproducts-cmfplonebefore 4.3.174.3.17

Same product

plone: all records

Other highest-scoring records for the same primary product.

  • CVE-2011-3587Unspecified vulnerability in Zope 2.12.x and 2.13.x, as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2, allows remote attacke
    60This week
  • CVE-2021-33509Plone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText transform
    40Plan
  • CVE-2020-35190The official plone Docker images before version of 4.3.18-alpine (Alpine specific) contain a blank password for a root user.
    40Plan
  • CVE-2020-7941A privilege escalation issue in plone.app.contenttypes in Plone 4.3 through 5.2.1 allows users to PUT (overwrite) some content without needi
    40Plan
  • CVE-2015-7293Multiple cross-site request forgery (CSRF) vulnerabilities in Zope Management Interface 4.3.7 and earlier, and Plone before 5.x.
    36Monitor
  • CVE-2021-33926An issue in Plone CMS v.
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
PyPI:plone4.3.16Package registry (OSV)
PyPI:plone5.1.0Package registry (OSV)
PyPI:products-cmfplone4.3.17Package registry (OSV)
PyPI:products-cmfplone5.0.10Package registry (OSV)
PyPI:products-cmfplone5.1.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records