Allowing Namespaces not working for us

  • Resolved kruddock

    (@kruddock)


    4 years, 3 months ago

    Hello Gregory,

    I have a few woocommerce sites. Are you saying there is no consistency in their namespaces? The sites I have do show “wc/v1”, “wc/v2″,”wc/v3” for WOO REST APIs.
    I’ve disabled REST API in the hardening section and then added wc/v3 as an allowable namespace, but I am unable to access wc/v3/products. Any ideas why I’m still getting locked out?

    Our namespaces according to /wp-json/

    “namespaces”: [
    “oembed/1.0”,
    “2fa/v1”,
    “contact-form-7/v1”,
    “yoast/v1”,
    “mc4wp/v1”,
    “wc/store”,
    “wc-analytics”,
    “wc-admin”,
    “testwp”,
    “elementor/v1”,
    “wc/v1”,
    “wc/v2”,
    “wc/v3”,
    “wccom-site/v1”,
    “wp/v2”
    ],

Viewing 1 replies (of 1 total)
  • Plugin Author gioni

    (@gioni)

    Hi! You have to add to the REST API white list “wc”, not “wc/v3”. Meaning WP Cerber makes no distinction between versions in the namespaces. As a namespace, you have to specify the string before the first slash /.

Viewing 1 replies (of 1 total)
  • The topic ‘Allowing Namespaces not working for us’ is closed to new replies.

Tags