Skip to main content
InfoAPIOWASP A01:2021CWE-862

How to fix: PUT method listed in Allow header

PUT changes server state. This is a passive observation that the endpoint's Allow header advertises PUT support (normal for any REST API with a PUT route, including properly authenticated ones); it does not confirm the endpoint accepts unauthenticated writes.

Why it matters

If PUT is genuinely unauthenticated, attackers can overwrite arbitrary resources: user profiles, configuration files, permissions, without any proof of identity. A single request can corrupt data for all users.

An Allow header listing PUT only confirms the verb is routed on this path, which is expected for any REST API with a PUT endpoint. It says nothing about whether that endpoint enforces authentication; a properly protected PUT route still advertises PUT in Allow for CORS purposes.

How to fix it

  1. 1Require authentication on PUT and reject anonymous writes at the proxy or framework layer
  2. 2Validate that the authenticated user owns the resource being updated
  3. 3Use an allowlist of updatable fields to prevent mass assignment

Code examples

Express: authenticated PUT with ownership check

JavaScript
router.put('/users/:id', requireAuth, async (req, res) => {
  if (req.user.id !== req.params.id && !req.user.isAdmin) {
    return res.status(403).json({ error: 'Forbidden' });
  }

  const { name, email, bio } = req.body;
  await db.users.update(req.params.id, { name, email, bio });
  res.json({ success: true });
});

References

Detected automatically by VulnRadar. The check id is api-rest-allow-methods-put-no-auth, stable across every scan so you can filter or diff on it.

See every api check

Questions

How severe is PUT method listed in Allow header?
VulnRadar rates this info severity in the api category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id api-rest-allow-methods-put-no-auth, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does PUT method listed in Allow header map to?
It maps to CWE-862. In the OWASP Top 10 it falls under A01:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for put method listed in allow header

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: PUT method listed in Allow header | VulnRadar