Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ GHSA-f7qw-5fgj-247x — plone-app-contenttypes

⚪ Unknown ✅ No Known Exploit CWE-601 OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Cross-site Scripting and Open Redirect in plone.app.contenttypes

Impact

Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen page in a cache, for example in Varnish.

The technique is known as cache poisoning.

Any later visitor can get redirected when clicking on a link on this page.

Usually only anonymous users are affected, but this depends on your cache settings.

Patches

New versions of plone.app.contenttypes have been released.

Version 2.2.3 works on Plone 5.2 and will be included in Plone 5.2.7.

Version 3.0.0a9 works on Plone 6 and will be included in Plone 6.0.0a3.

Note that the Products.CMFPlone package has the same problem in the 4.3 series.

In Plone 5.0-5.2, the default Products.ATContentTypes version has the same problem. See [advisory](https://github.com/plone/Products.ATContentTypes/security/advisories/GHSA-g4c2-ghfg-g5rh).

For all unpatched versions of the three packages, you can use the following workaround.

Workaround

Make sure the image_view_fullscreen page is not stored in the cache.

In Plone:

  • Login as Manager and go to Site Setup.
  • Go to the 'Caching' control panel. If this does not exist, or 'Enable caching' is not checked, you should normally not be vulnerable.
  • Click on the tab 'Caching operations'.
  • Under 'Legacy template mappings' locate the ruleset 'Content item view'.
  • From the last column ('Templates') remove 'image_view_fullscreen'.
  • Click on Save.

Reporter

This vulnerability was responsibly disclosed to the Plone Security Team by Gustav Hansen, F-Secure Consulting. Thank you!

For more information

If you have any questions or comments about this advisory, email us at [security@plone.org](mailto:security@plone.org)

This is also the correct address to use when you want to report a possible vulnerability.

See [our security report policy](https://plone.org/security/report).

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

GHSA-f7qw-5fgj-247x is classified as CWE-601: Open Redirect. A redirect target is taken from user input, so a trusted link can send the visitor to an attacker's site.

Affected software

GHSA-f7qw-5fgj-247x is recorded against 1 package.

  • plone-app-contenttypes (fixed in 2.2.3)

Timeline and source

Published on 1 February 2022 and last revised on 5 December 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Package)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
CWE CWE-601
Public Exploit ✅ No
Source OSV
Published 2022-02-01
Updated 2026-08-20
Modified 2024-12-05
Fix URL N/A

Affected Packages

Software From version Fixed in
plone-app-contenttypes 2.2.3

Similar Threats

Free Vulnerability Check

Is your site affected by GHSA-f7qw-5fgj-247x?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against GHSA-f7qw-5fgj-247x and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.