Skip to content
Heist/ feed
Back to feed
Medium

Contao's remember-me tokens will not be cleared after a password change

Type: advisorySources: OSV

Contao is an open source content management system. Prior to version 4.13.40, when a frontend member changes their password in the personal data or the password lost module, the corresponding remember-me tokens are not removed. If someone compromises an account and is able to get a remember-me token, changing the password would not be enough to reclaim control over the account. Version 4.13.40 contains a fix for the issue. As a workaround, disable "Allow auto login" in the login module.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2024-30262
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 13:42 UTC · Revision 1

Source evidence

Contao's remember-me tokens will not be cleared after a password change

core-osv · Original source

Published 9 Apr 2024, 16:45 UTC

Contao is an open source content management system. Prior to version 4.13.40, when a frontend member changes their password in the personal data or the password lost module, the corresponding remember-me tokens are not removed. If someone compromises an account and is able to get a remember-me token, changing the password would not be enough to reclaim control over the account. Version 4.13.40 contains a fix for the issue. As a workaround, disable "Allow auto login" in the login module.

osv:CVE-2024-30262
Complete source record
{
  "id": "1370a19846a3852cd8db41452354de67b0e9fa85c62a6caf11d4108f1552d295",
  "url": "https://osv.dev/vulnerability/CVE-2024-30262",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Contao's remember-me tokens will not be cleared after a password change",
    "summary": "Contao is an open source content management system. Prior to version 4.13.40, when a frontend member changes their password in the personal data or the password lost module, the corresponding remember-me tokens are not removed. If someone compromises an account and is able to get a remember-me token, changing the password would not be enough to reclaim control over the account. Version 4.13.40 contains a fix for the issue. As a workaround, disable \"Allow auto login\" in the login module.",
    "evidence": "osv:CVE-2024-30262",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2024-30262",
      "aliases": [
        "CVE-2024-30262",
        "GHSA-r4r6-j2j3-7pp5"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/contao/contao",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "1789b18b3d2b56c0dd17dc45e870c472a47d536f"
                },
                {
                  "fixed": "3032baa456f607169ffae82a8920354adb338fe9"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "4.13.40"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "range": [
                      {
                        "fixed": "3032baa456f607169ffae82a8920354adb338fe9"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  }
                ]
              }
            }
          ],
          "versions": [
            "4.13.39",
            "4.13.38",
            "4.13.37",
            "4.13.36",
            "4.13.35",
            "4.13.34",
            "4.13.33",
            "4.13.32",
            "4.13.31",
            "4.13.30",
            "4.13.29",
            "4.13.28",
            "4.13.27",
            "4.13.26",
            "4.13.25",
            "4.13.24",
            "4.13.23",
            "4.13.22",
            "4.13.21",
            "4.13.20",
            "4.13.19",
            "4.13.18",
            "4.13.17",
            "4.13.16",
            "4.13.15",
            "4.13.14",
            "4.13.13",
            "4.13.12",
            "4.13.11",
            "4.13.10",
            "4.13.9",
            "4.13.8",
            "4.13.7",
            "4.13.6",
            "4.13.5",
            "4.13.4",
            "4.13.2",
            "4.13.1",
            "4.13.0",
            "4.13.0-RC3",
            "4.13.0-RC2",
            "4.13.0-RC1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-30262.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:35.894688979Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/30xxx/CVE-2024-30262.json",
        "https://github.com/contao/contao/security/advisories/GHSA-r4r6-j2j3-7pp5",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-30262",
        "https://github.com/contao/contao/commit/3032baa456f607169ffae82a8920354adb338fe9"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-384",
          "CWE-613"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/30xxx/CVE-2024-30262.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-30262",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 503231,
  "published_at": "2024-04-09T16:45:57.132+00:00"
}